...
PUT /loyalty/v2/updateBasket
Headers
We will use the same headers as the Partner API.
Authentication and authorization will use the bearer Bearer token in JWT format , which includes the API key, and identifies the following, based on this documentation: as specified in /wiki/spaces/IN/pages/3739288100
...
.
...
...
Region (e.g. UK)
...
Sub, which is the integration partner (e.g. NCR, Khumbu)
...
Partner ID, which uniquely identifies the partner configuration which will give us more details if we need.
Body
transactionId<UUID>: unique identifier of the Loyalty transaction to be updated.<TBC - scan code><TBC - basket contents>
Example request
| Code Block |
|---|
{
"transactionId": "f4190848-169d-4c69-9f53-f916318c432b",
"code": 992342
} |
Response Format
| Warning |
|---|
Content from this point onwards has not been updated. |
...
| Info |
|---|
All error responses use the standard Error Response Responses format. |
HTTP
400 (Bad Request)if the request body has an incorrect format. In this case, the response will include details about which specific field or fields have an incorrect format.HTTP
401 (Unauthorized)if the bearer token is missing or not valid.HTTP
403 (Forbidden): if the specifiedidentifieris not valid.HTTP
404 (Not Found): if the specifiedstoreIdwas not found.