Safe Stamper Web API: Difference between revisions
Jump to navigation
Jump to search
w>Jguillo No edit summary |
w>Jguillo |
||
| Line 12: | Line 12: | ||
All operations may be called by POST or GET, and return their results in JSON format. | All operations may be called by POST or GET, and return their results in JSON format. | ||
== Authentication == | |||
For authentication, all requests must include a signature parameter calculated from the request parameters and the API client private key. | |||
* [[Safe Stamper Web API parameters signature]] | |||
== API operations == | |||
* [[stamp]]: Send URLs to certificate | * [[stamp]]: Send URLs to certificate | ||
* [[status]]: Check the status of a certification job | * [[status]]: Check the status of a certification job | ||
== Callbacks == | |||
When calling [[stamp]] you can provide a callback URL: | When calling [[stamp]] you can provide a callback URL: | ||
* [[Safe Stamper Web API callbacks]] | * [[Safe Stamper Web API callbacks]] | ||
Revision as of 11:03, 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
API reference
All operations may be called by POST or GET, and return their results in JSON format.
Authentication
For authentication, all requests must include a signature parameter calculated from the request parameters and the API client private key.
API operations
Callbacks
When calling stamp you can provide a callback URL: