v1
latestOpenAPI 3.0.32026-07-243003151.2 MBSpend
This API applies the calculated operations from the spend-calculate API to a wallet and spends points from a customer's points account. This creates an active Wallet Transaction in the wallet found by the identity passed into the request.
Headers
This request HTTP header advertises which content encoding (usually a compression algorithm) the calling application is able to understand. The server selects one of the proposals, use it and informs the client of its choice with the Content-Encoding Response header. Currently supported gzip and deflate. Please note if this request header is not present, no compression will be used.
This general HTTP header controls (or rather influences) whether the network connection stays open after the current request finishes. If the sent value is keep-alive, the connection should stay in a special state, allowing to be reused for subsequent requests to the same server. Please note these connections will be closed after reaching timeout threshold controlled by EES server (usually after 5 seconds).
Standard HTTP header to inform EES API what type of content was passed in request payload
Client ID, This will be provided by EES and is unique to the company calling the API.
Request Security Hash, calculated using SHA-256 function from concatenated full Request URI Path with Query String(s), Payload and Client Secret
Unique Reference for the API transaction within the calling company.
Optional header provided by the calling application for EES AIR to identify what was the external Subsystem Id / Name.
Optional header(s) provided by the calling application to EES AIR. Please note this header name has to follow pattern X-CUSTOM-*
Request body
Example request
{
"transactionDetails": {
"key1": "Value1",
"key2": "AnotherValue"
}
}Response
Response payload from calling the spend endpoint