Which file system to use?
Signzy provides a suite of APIs that can be used to process various types of documents and files. These APIs use cutting-edge technologies such as artificial intelligence and machine learning to extract information from documents accurately and quickly.
The Signzy APIs that work on documents such as OCR, face match, PDF conversions, and document signing, require clients to provide the file as a URL. This is to allow the APIs to access the file and extract the relevant information.
In the context of Signzy APIs, clients need to provide a URL to a file for the API to process the document or file. The URL allows the API to access the file and extract relevant information such as text, images or signatures.
To obtain a URL to a file, clients can use a system that provides URL hosting services. Such systems allow users to upload files and obtain a direct link to the file that can be used to access the file from anywhere in the world.
Which file management systems can I use?
Popular systems that provide such services include Amazon Web Services (AWS) S3, Google Cloud Storage, Microsoft Azure Blob Storage, and Dropbox. These services are widely used by businesses of all sizes to store and share files securely with colleagues or clients.
Constraints:
- Clients using file hosting services for Signzy APIs must ensure the system allows HEAD requests, which Signzy APIs use to check file availability and status before processing.
- To ensure efficient processing by Signzy APIs, URLs for files to be processed should be directly accessible and not behind a CDN that may require a bot check, such as Cloudflare.
In addition to these popular systems, Signzy also provides its own file hosting service called Persist. With Persist, clients can upload files and obtain a direct URL to the file that can be used with Signzy's OCR, face match, PDF conversions, and document signing APIs.
See more details about Signzy Persist API specifications.
Security of Persist file system
Signzy's Persist API not only offers a convenient way to exchange files but also ensures secure exchange of sensitive data.
The URL for a file uploaded to Signzy's Persist API has two components: a numerical component and a key component in the filename. For example, in the URL https://persist.signzy.tech/api/files/0000000000/download/XXXXXXXXXXXXXXXXXXXXXXXXXXX.png, "0000000000" is the numerical component, while "XXXXXXXXXXXXXXXXXXXXXXXXXXX.png" is the key component.
The numerical component of the URL is a unique identifier assigned to each client. This helps Signzy to keep track of which client has uploaded the file. The key component is a randomly generated string that makes it difficult for unauthorized parties to access the file.
In addition, the Persist API provides a time-to-live (TTL) parameter that ensures that files uploaded to the API are purged after a set period. The TTL parameter specifies the time for which the file will be stored before being automatically deleted. This helps to maintain data privacy by ensuring that files are not stored for longer than necessary.
Furthermore, Signzy stores all files in an encrypted format using AES-256 encryption, ensuring that files are stored securely. The API also uses secure communication protocols such as HTTPS to ensure that data transmitted between the client and the API is encrypted and secure.
Signzy's Persist API provides a secure way to exchange files by assigning unique numerical components to clients and using randomly generated key components in filenames. The TTL parameter ensures that files are purged after a set period, and all files are stored securely in an encrypted format using AES-256 encryption.