API secret
The API secret section lets you generate OAuth client-id and client-secret that you need in order to perform API requests as described in authenticating with the API section below.
Click on Create API client credentials button to generate client credentials.
You should see next modal window with Client id and Secret.
🔑 Make sure to write down your Secret, because it’s shown only once after generation and you will have to regenerate your secret or create new credentials if you lose it.
❗️API secrets do not have expiry dates. Make sure to delete all unused or possibly compromised secrets immediately.
Authenticating with the API
When getting started with our Salv API, you need to generate your client-id and client-secret as described in the API secret section above. Your systems will need to exchange these for a temporary bearer token, which you will then use to perform the actual API requests.
Here is an example cURL command to do the initial authentication:
curl -X POST <https://demo.salv.com/oauth/token> -d "grant_type=client_credentials" --user your-client-id:your-client-secret
Use demo.salv.com or app.salv.com as the server name depending on whether you'll request info from demo or live environment. Replace the your-client-id and your-client-secret values with your actual credentials.
If all is well, you will see this kind of response.
{"access_token":"long-token-value","token_type":"bearer","expires_in":43199,"scope":"aml","customerId":9,"jti":"92cae308-1e2d-4e87-b26d-bad3a737cf16"}The important piece here is the access_token value. You will need to capture this value and use it for actual API requests according to the developer documentation.
⬇️ API definition to import into Postman can be downloaded at https://docs.salv.com/api/public.yaml.