edge.e-attestations.io Open in urlscan Pro
54.161.92.125  Public Scan

Form analysis
0 forms found in the DOM

Text Content

Public


Documentation Settings

ENVIRONMENT
EA-Production

LAYOUT
Double Column

LANGUAGE
cURL - cURL



e-Attestations EDGE API
Introduction
e-Attestation 'EDGE' API, the restful API
Authenticate
Account information
Requirements
Thirdparties
Dossiers
Dossiers creation & Processes
Dossiers updates
Dossier's notes
Dossier's documents
Dossier's Evidences & Files
Errors codes


E-ATTESTATIONS EDGE API


E-ATTESTATION 'EDGE' API, THE RESTFUL API

https://e-attestations.io

The REST / Json e-Attestations API is used to interface a client information
system with the e-Attestations platform following the HTTP protocol.

Our APIs contain predictable resource-oriented URLs, accept request bodies
encoded in [JSON] format , return encoded responses [JSON] and uses standard
HTTP response codes, authentication and verbs.

'Client' applications using the e-Attestations REST API enrich the Client
Information System with the catalog of e-Attestations data and services in a
secure and very flexible manner.

The API can also be used by integrators, software publishers, SAAS solutions or
connectors.


POSTMAN COLLECTION

This collection of Postman scripts can ease testing phase.


REQUESTS AND SCENARIOS

We provide you with a set of requests for very common scenario you will find
with the use of e-Attestations EDGE API.

Of course they are quite simple examples.

For each endpoint, there are one or more examples, you can see theme on the
right panel :



More document evidences examples can be found in the Dossier's Evidences & Files
Evidences section in this documentation : SIS-ID, Trustpair etc.
Indeed, automatic processing provides additional information :



Feel free to contact us for more advanced questions.


POSTMAN ENVIRONMENT AND VARIABLES

All requests will fetch a new access_token automatically based on variables in
your Postman environment.

This collection use a script that will automatic fetches for you :

   
 * access_token : the JWT access token needed for each request
   
 * account_id : the first account found in account_ids from the JWT
   

This 2 variables are mandatory and generated automatically for each request.

You can swicth from environment to another and load values for the following
variables.

   
 * username : your username
   
 * password : your password
   
 * ea_auth_serv : the url for e-Attestations authorizer
   
 * ea_api_serv : the url for API services
   

This credentials are provided by e-Attestations. Please contact e-Attestations
API Manager by email at api@eattestationscom.zohodesk.eu


QUICK START

   
 * Download this Postman collection :
   



   
 * Select the e-Attestations environment (EA-Production) and fill your username
   and password in the environment variables section :
   



   
 * You can test your integration by using a test environment ( contact
   e-Attestations API Manager by email if you need it). To do so, you have to
   configure a new Postman environement :
   



 * ea_auth_serv : https://auth.e-attestations.com to
   https://auth.test-e-attestations.com

 * ea_api_serv : https://edge.e-attestations.com to
   https://edge.test-e-attestations.com

 * username and password for the demo environement ( provided by e-Attestations)
   

   
 * Now, you can test all endpoints and switch from one environment to another
   

AUTHORIZATIONBearer Token