​
Idempotent Requests

Endpoints in this section support idempotency, which means that you can safely submit identical requests without making changes to the data storage twice. To perform an idempotent request, provide x-idempotency-key header with the request.

Idempotency works by saving URL, method, and idempotency header of your request as a key and the result of the request as value for 24 hours.

In case an error occurs while processing the request, the error message will be persisted and resent on possible retries. Please note that fields of uuid and timestamp fields of the error will be regenerated to be able to track down the identity of each error.

Idempotency key needs to be a unique value generated by the client which server then uses to activate the feature to be able to recognize possible future retries of the same request. The max length of the idempotency key is 64 characters.

​
Endpoints

Update a Multi-application card

PATCH /v1/MULTI_APPLICATION_CARD/{id}

Update Card

POST /v3/{id}/update/{propertyToUpdate}

Update a Mastercard branded card

PATCH /v4/MC_CARD/{id}

Update a virtual Mastercard branded card

PATCH /v4/MC_VIRTUAL/{id}

Update a debit Mastercard branded card

PATCH /v4/DEBIT_MC/{id}

Update a virtual debit Mastercard branded card

PATCH /v4/DEBIT_MC_VIRTUAL/{id}

Update a VISA branded card

PATCH /v4/VISA_CARD/{id}

Update a virtual VISA branded card

PATCH /v4/VISA_VIRTUAL/{id}

Update a debit VISA branded card

PATCH /v4/DEBIT_VISA/{id}

Update a virtual debit VISA branded card

PATCH /v4/DEBIT_VISA_VIRTUAL/{id}

Update a fleet card

PATCH /v4/{fleetTemplate}/{id}

Update Card (Deprecated)

PATCH /v3/{id}