Tracking Hub API

Download D1-Public-IN-v1-Physical-Issuance.json

Track Card

post

https://api.d1.thalescloud.io/banking/v1https://api.d1-stg.thalescloud.io/banking/v1

/issuers/{issuerId}/physicalCards/{cardId}/track

This API is used by the issuer backend to request the shipment tracking of any card not personalized by Thales

Authorizations

bearerAuth

AuthorizationstringRequired

A JWT generated by the get token API.
The server checks the validity of the provided token to control access to this protected resource. Please refer to Authorization flow for more details about the flow and on how to get this JWT.

Path parameters

issuerIdstring · min: 10 · max: 10Required

The id of the issuer

cardIdstring · min: 1 · max: 48Required

Unique identifier of the card.

Pattern: ^[A-Za-z0-9_-]{1,48}$

Header parameters

x-correlation-idstringOptional

Random identifier which can be used to correlate the different API calls done as part of a single use-case. This identifier will be the one primarily used for troubleshooting.

Warning: This identifier should not be derived from sensitive personal data, as its value will be logged in clear.

There is no strong guarantee of the uniqueness of this identifier, so please refrain from using it for other purpose than logging and troubleshooting.

Pattern: ^[A-Za-z0-9_-]{1,64}$

Body

application/json

or

or

Responses

202

Successful track card request

application/json

400

Bad request due to invalid URI, headers, parameters, or payload.
The below table defines the possible errors: | errorCode | error | Retry Possible | Comments | | -------------- | ------------| ----------| -----------------------------------| | - | - | no | General error with no further information provided. | | FIELD_INVALID_FORMAT | Field in error (first found) | no | A field does not match the expected format specified in the documentation. | | CRYPTO_ERROR | - | no | Decryption of the provided encrypted data failed. | | FIELD_INVALID_VALUE | Field in error (first found) | no | A field value is not permitted for the specified field. | | PARSING_ERROR | Field in error (first found) | no | Encrypted data is not a valid JSON string. |

application/json

401

Unauthorized request due to missing or invalid access token.

errorCode	error	Retry Possible	Comments
-	-	no	General error with no further information provided.
AUTHORIZER_UNAUTHORIZED	Unauthorized message	no	Access token not valid

application/json

403

Request forbidden by authorization rules or business constraints.
The below table defines the possible error:

errorCode	error	Retry Possible	Comments
-	-	no	General error with no further information provided.
AUTHORIZER_FORBIDDEN	not_authorized error message	no	The user is not authorized to access the requested resource.
OPERATION_NOT_ALLOWED	Name of the operation/field that is not allowed in this operation	no	The specified operation or field is not permitted for this card product.

application/json

404

Requested resource not found.

application/json

500

Internal server error while processing the request. The below table defines the possible error:

errorCode	error	Retry Possible	Comments
-	-	no	General error with no further information provided.
INTERNAL_ERROR	Error details (if any)	no	The server encountered an issue while processing the request.

application/json

503

The service is temporarily unavailable. You may retry your request later.

post

/issuers/{issuerId}/physicalCards/{cardId}/track

HTTPcURLJavaScriptPython

POST /banking/v1/issuers/{issuerId}/physicalCards/{cardId}/track HTTP/1.1
Host: api.d1.thalescloud.io
Authorization: Bearer YOUR_SECRET_TOKEN
Content-Type: application/json
Accept: */*
Content-Length: 173

{
  "trackingType": "SHIPMENT",
  "trackingNumber": "61293150000079650811",
  "shipmentDate": "2023-01-21T17:32:28Z",
  "productionSite": "London",
  "postalCode": "WC2N5DU",
  "countryCode": "GB"
}

Shipment trackingProduction trackingReturn tracking

{
  "operationId": "text"
}