Our API is based on REST and uses simple, predictable URLs. It sends and receives data in JSON format.
You interact with the API using standard HTTP methods such as GET, POST, and PUT, and responses follow standard HTTP status codes. All API requests must be made over HTTPS. Requests sent over plain HTTP are not supported.
Authentication
Our API uses request-signature-based authentication. You will need a secret API key and a vendor number provided by Evrotrust in order to access our API.
Every request must include an authorization header containing a cryptographic signature that is generated from your secret API key and the request body. No separate token request is required; each request is self-authenticated using your API key.
Environments
Testing
You can test our API in the testing environment, which closely mirrors the production setup for controlled testing.
https://et.test.iteco.bg/vendor
Production
When you take your integration live, make sure it targets the production environment.
https://v.evrotrust.com/vendor/
Response codes
We rely on standard HTTP status codes to communicate whether an API request was processed successfully or not. In general:
- 2xx status codes indicate a successful request.
- 4xx status codes indicate a client-side error, such as a missing or invalid required parameter.
- 5xx status codes indicate an internal Evrotrust server error, which should occur only in exceptional cases.
Not all error conditions can be mapped unambiguously to HTTP status codes. The following section provides a detailed breakdown of possible responses:
| HTTP Code | Description | Details |
|---|---|---|
| 200 | OK | The request was successful. |
| 204 | The request was successful, but the response returns no body. | |
| 400 | Invalid data supplied | The request was invalid, usually because a required parameter wasn't set. The required ones are PID*, phone and document number. The response includes the missing parameter, for example: “user document number is required”. -For agent the only required parameter is PID*. You’ll receive this response if either the agent’s PID is incorrect or the agent with the sent PID is not added. -For a document, the required parameters are "description" and "coverage". If one of them is not sent, you’ll receive this response. |
| 401 | Unauthorized | There was an error with either the Vendor number or the API Key. The error may lay in the calculation of the authorization header. |
| 438 | User not found | |
| 449 | User data is not valid | You’ll receive this response if the user’s PID* or document’s number incorrect during the check in the system of the Ministry of Interior. Apart from the aforementioned error, the document may be expired, invalid, stolen or revoked due to the user being detained. |
| 450 | File exceeds max allowed file size | The allowed size is between 5 and 30 MB depending on your contract. Usually, it is 5 MB. |
| 454 | Incorrect coverage | Parameter "coverage" could be 0, 500, 20000, 100000, 250000. The amount is in euro. 0 stands for unlimited. The default should be set at 20000. |
| 457 | Not supported file types. | |
| 469 | The request can not be processed | Try again in 60 seconds. - This response is due to an error in the communication with the system of the Bulgarian Ministry of Interior; the user’s data cannot be checked. |
Testing
For each request, we provide a code example that you can adapt by setting the required and optional parameters as needed and execute directly from the command line.
If you prefer to test the API with Postman, refer to the Postman Section.
Support
For more information and assistance pls refer to https://support.evrotrust.com/ or contact [email protected]