Certifying digital evidence after every manual operation can be time-consuming and make it difficult to track hundreds of cases. Integrating certification into business systems helps reduce these repetitive tasks.
A REST API for digital evidence certification connects applications to a certification platform. It allows businesses to request certification operations, manage results and link certificates to internal processes.
At SaveTheProof, we offer this capability through our Flat Rate + API plan. In this guide, we explain how to plan your integration, what digital evidence to document and which controls you need to automate certification securely.
What Is a REST API for Digital Evidence Certification?
A REST API is an interface that enables applications to exchange requests and responses using web technologies such as HTTP. Its operations must follow the provider’s technical documentation.
Automated digital evidence certification allows businesses to initiate and manage certification operations from a CRM, ERP, document management system or custom application, without manually repeating every action on a website.
According to Postman’s State of the API 2025 report, REST has a 93% adoption rate among the surveyed participants. The study involved more than 5,700 professionals from different countries.
This figure describes the international API ecosystem, not the Spanish digital evidence market. Source: Postman’s State of the API 2025 report.
- Triggering event: a business action that requires information to be documented, such as registering a customer complaint.
- Request: a communication containing the data needed to initiate certification.
- Result: the certificate and supporting documentation available once the operation is complete.
- Traceability: a verifiable link between the triggering event, the request and the files generated.
What Can You Certify via API: Web Pages, Browsing Sessions and Files?
The Flat Rate + API plan includes web page, browsing session and file certificates. Choosing the appropriate option depends on what you need to document and which operations are supported by the API.
- Web page: preserves an accessible version of a public URL, such as an online offer or a set of commercial terms and conditions.
- Browsing session: documents authorised steps and interactions, such as an online purchasing process or content accessed after signing in.
- File: identifies documents, images or videos and allows their data to be checked using a SHA-256 cryptographic hash.
An online retailer can associate certificates with changes to promotional offers, an insurance company can link them to claim documents, and a legal team can document a relevant browsing session.
The fact that a subscription includes all three certificate types does not mean that every operation can be performed through the API. Confirm the available functions and requirements for each operation before designing your workflow.
How to Integrate the SaveTheProof REST API: Step-by-Step Guide
A reliable API integration begins before any code is written. Define what needs to be certified, who is authorised to request certification and how the result will be retrieved once the operation is complete.
You can access our technical documentation at https://www.savetheproof.com/en/api-integration/. From there, we link to our Postman API reference so you can review the operations currently available.
- 1. Define your use case: identify the event that triggers certification and the case or record to which the evidence will be linked.
- 2. Choose the certificate type: distinguish between public URLs, interactive browsing sessions and files to avoid using an unsuitable certification method.
- 3. Review Flat Rate + API: confirm the subscription terms, user accounts, storage capacity and operational limits.
- 4. Study the documentation: examine authentication requirements, input data, responses and error handling.
- 5. Run tests: use information you are authorised to process and test both successful and unsuccessful requests.
- 6. Store the references: link each available result to the corresponding case or record identifier in your system.
- 7. Monitor operations: preserve the documentation, manage incidents and review the process regularly.
Do not assume that the API supports webhooks, queues, automatic retries or idempotency keys. Your technical team should confirm these capabilities before relying on them.
For example, a case management system may request certification of a file associated with a complaint. If the operation fails, the system should record the incident before attempting it again.
The objective is not to automate without oversight, but to replace repetitive manual actions with a verifiable procedure involving clearly assigned responsibilities and identifiable records.
Traceability, Security and Legal Validity of Automated Certifications
Centralised control means maintaining a record that shows which certification operation was requested, its outcome and where the associated documentation is stored.
We recommend retaining the following information in your own system, where available, without assuming that every item corresponds to a native field in our API:
- Internal reference: the case, file or process identifier that triggered the certification request.
- Type and source: the certificate type and the URL, file or process being documented.
- Dates and times: when the request was submitted and completed, based on the available records.
- Result: the reference for the issued certificate or information about any incident.
- Evidence storage: the location of the PDF certificate and associated files, together with their access permissions.
- Errors and duplicates: records of failures, checks before retrying requests and reconciliation of certification operations.
It is also advisable to monitor completed certifications, failures, processing times and storage usage. These are internal performance indicators, not service performance guarantees provided by SaveTheProof.
One useful metric is the success rate: the number of completed certifications divided by the number of valid requests. Record the reporting period and evidence type to make meaningful comparisons.
The Flat Rate + API plan includes unlimited certifications, but the subscription terms specify one concurrent certification per user. You should account for this restriction when planning for peak demand.
Our certificates incorporate advanced electronic signatures. For qualified electronic timestamping, we work with external qualified trust service providers.
Article 41 of the EU eIDAS Regulation establishes legal presumptions regarding the accuracy of the date and time and the integrity of data linked to a qualified electronic timestamp. It does not establish the truthfulness of the certified content or guarantee a favourable judicial assessment.
Consult the eIDAS Regulation on EUR-Lex. You should also implement appropriate controls for credentials, data protection, access permissions and evidence retention according to the requirements of each case.
Frequently Asked Questions About REST API Integration
Is Postman Required to Integrate the REST API?
No. Postman allows developers to consult the documentation and test API operations. The integration can be developed using any other system compatible with the published technical requirements and supported operations.
What Is the Difference Between the REST API and WebTrack?
The REST API connects applications to certification functions. WebTrack enables website monitoring and is included among the features available with certain subscription plans.
How Can I Verify a Certificate Generated Through an API?
You can upload the PDF certificate to our free online verification tool to check whether it is valid and has not been tampered with: https://secure.savetheproof.com/verify.
Integrate the REST API with SaveTheProof Flat Rate + API
At SaveTheProof, we offer Flat Rate + API from €249/month, including taxes, with 10 GB of storage and unlimited certifications across all three certificate types, subject to the applicable subscription terms.
The plan also includes WebTrack and bulk web page certification. We do not offer these features as standalone commercial services outside their corresponding subscription plans.
To get started, identify your business processes, determine what digital evidence you need to preserve and consult our technical documentation. We can help you assess the integration and its requirements before deploying it into production.
Request information through our contact form. Automate your digital evidence certifications with traceability, security and retention controls suited to your organisation.
