Rebuild API (Shared)
Powered by d-FIRST™, Glasswall Rebuild harnesses the world's most advanced CDR technology.
Regenerating every file to a standard of ‘known good’, Glasswall's Rebuild API delivers unparalleled levels of security and integrity, ensuring only safe and clean files reach users. Sub-second processing and a seamless user experience leave business critical communications uninterrupted.
Sending files to the Glasswall Rebuild API returns safe, clean regenerated versions:
- Verified as the correct file type
- Meets structural specification for the identified file format with all deviations remediated
- High risk Active Content removed
Glasswall Rebuild API empowers development teams dealing with files to do so in a clean safe way where the files are rebuilt to known good.
Along with an API key, users upload files they want to rebuild to known good. Keys are purchased based on required file volume. The file is rebuilt by our cloud service with the resulting rebuilt file returned. All uploaded files are immediately destroyed, ensuring complete protection of your data.
For more information visit our Engineering Site, where you can find:
- How to Guides
- Code Samples
- Supporting Documentation
Here are all the different types of files the Glasswall Rebuild engine detects using the internal structure of files:
|File Types||File Description|
|Adobe Portable Document|
|JPG GIF PNG EMF WMF TIFF GeoTIFF BMP||Images|
|DOC DOT||MS Word 97-2003|
|XLS XLT||MS Excel 97-2003|
|PPT POT||MS PowerPoint 97-2003|
|DOCX DOCM DOTX DOTM||MS Word 2003 & later|
|XLSX XLAM XLSM XLTX XLTM||MS Excel 2003 & later|
|XPPTX POTX POTM PPTM PPSX PPAM PPSM||MS PowerPoint 2003 & later|
Before you integrate Rebuild into your solution, be aware that file in the HTTP body only supports files up to 6MB due to a limitation in the request payload to AWS Lambda. If your use case deals with larger files, please use the input URL based pathway which currently supports files up to 30MB On the shared platform the amount and rate of calling our API is controlled by a usage plan.
By default accounts on our shared platform are limited to 50 requests per second. Exceeding these rates results in throttling and the appearance of the 429 HTTP code response. If this is an issue, you might want to consider moving to our dedicated model where the full rate can be assigned.
For more information visit our Engineering Site