Safe Stamper Web API: Difference between revisions
Jump to navigation
Jump to search
w>Jguillo |
w>Jguillo |
||
| Line 19: | Line 19: | ||
= Callbacks = | = Callbacks = | ||
When starting a certification job with [[stamp]] you can provide a callback URL | When starting a certification job with [[stamp]] you can provide a callback URL. | ||
Once the certification job is finished, the callback URL will receive a POST call with the same JSON object as returned in the [[status]] operation. | |||
To authenticate the callback, the request body HMAC-SHA1 will be calculated using the API client private key and will be provided as a query string parameter ''signature'' | |||
== Example == | |||
<pre> | |||
POST http://my.domain.com/stamper-callback?signature= | |||
Content-Type: application/json | |||
{jobId: | |||
</pre> | |||
= Example = | = Example = | ||
Revision as of 10:28, 19 April 2016
API keys
To use Safe Stamper Web through API, you need a pair of keys:
- A shared key that identifies your client application
- A private key used for signing your requests
To get your pair of API keys, you can contact us through Safe Stamper contact form
Parameters signature
Safe Stamper Web API parameters signature
API operations
All operations return their results in JSON format.
Callbacks
When starting a certification job with stamp you can provide a callback URL.
Once the certification job is finished, the callback URL will receive a POST call with the same JSON object as returned in the status operation.
To authenticate the callback, the request body HMAC-SHA1 will be calculated using the API client private key and will be provided as a query string parameter signature
Example
POST http://my.domain.com/stamper-callback?signature=
Content-Type: application/json
{jobId: