Add Card Number to a Card Series

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

Example request

curl --location 'https://eu.api.capillarytech.com/v2/card' \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Basic <BASE64_CREDENTIALS>' \
  --header 'Cookie: <COOKIE>' \
  --data '{
    "seriesId": 224,
    "cardNumber": "ghost0000800001180930",
    "cardExternalId": "CardExternal6993",
    "statusLabel": "NOT_ISSUED",
    "statusInfo": {
        "reason": "Card is generated but not issued"
    }
}'

Prerequisites

RequirementDetails
Authentication detailsAuthorization header with Basic Auth (Base64-encoded username:password)
Access permissionWRITE access to the Card resource. See Access Group configuration.

Resource information

Pagination supportNo
Batch supportNo

Request body parameters

FieldTypeRequiredDescription
seriesIdNumberYesUnique identifier of the card series to which the card number will be added. Must correspond to an existing series in the system.
cardNumberStringYesUnique card number to be added to the series. Must not already exist in the system.
statusLabelStringYes

Status of the card at the time of creation. Must be a valid label configured for the CARD entity type.

Supported values: NOT_ISSUED, ACTIVE, SUSPENDED, ISSUED, DELETED, EXPIRED

Default value:NOT_ISSUED

cardExternalIdStringNoExternal identifier for the card. Must be unique if provided.
statusInfoObjectNoAdditional metadata associated with the card status.
statusInfo.reasonStringNoDescription of the reason for the current card status. Example: "Card is generated but not issued".
seriesCodeStringNoUnique code of the card series. Can be used as an alternative to seriesId if seriesId is not provided.
customerIdNumberNoUnique identifier of the customer to associate with the card at the time of creation.
extendedFieldsObjectNoKey-value pairs representing extended field values for the card. Keys must match the configured extended fields for the organization.
customFieldsObjectNoKey-value pairs representing custom field values for the card.
mappedEntityObjectNoMapping details to associate the card with an entity such as a store, location, or till.

Example response

{
    "entity": 966091,
    "warnings": []
}

Response parameters

FieldTypeDescription
entityNumberThe unique ID of the newly created card.
warningsArrayList of warning objects generated during the request. Empty array if no warnings.

Error codes

CodeTypeDescription
400ErrorInvalid request. Check that all required fields (seriesId, cardNumber, statusLabel) are present and valid.
401ErrorUnauthorised. Invalid or missing Authorization header.
403ErrorForbidden. The authenticated user does not have WRITE access to the Card resource.
404ErrorResource not found. The specified seriesId or seriesCode does not exist.
409ErrorConflict. The provided cardNumber or cardExternalId already exists in the system.
Body Params
string
Responses

Language
Credentials
Basic
base64
:
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json