Sign in

v50

latestOpenAPI 3.0.3Apache 2.0raw.githubusercontent.com2026-08-0342108400.9 KB
Readers

Create a Reader

Create a new Reader for the merchant account.

post/v0.1/merchants/{merchant_code}/readers

Path parameters

merchant_codestring required
Example:MK10CL2A

Short unique identifier for the merchant.

Request body

pairing_codestring required

The pairing code is a 8 or 9 character alphanumeric string that is displayed on a SumUp Device after initiating the pairing. It is used to link the physical device to the created pairing.

namestring required

Custom human-readable, user-defined name for easier identification of the reader.

metadataMetadata

Set of user-defined key-value pairs attached to the object. Partial updates are not supported. When updating, always submit whole metadata. Maximum of 64 parameters are allowed in the object.

Example request

{
  "pairing_code": "4WLFDSBF",
  "name": "Frontdesk",
  "metadata": {}
}

Response

Returns the Reader object if the creation succeeded.

idstring required

Unique identifier of the reader that the payment is initiated on.

namestring required

Custom human-readable, user-defined name for easier identification of the reader.

status'unknown' | 'processing' | 'paired' | 'expired' required

The status of the reader object gives information about the current state of the reader.

Possible values:

  • unknown - The reader status is unknown.
  • processing - The reader is created and waits for the physical device to confirm the pairing.
  • paired - The reader is paired with a merchant account and can be used with SumUp APIs.
  • expired - The pairing is expired and no longer usable with the account. The resource needs to get recreated.
metadataMetadata

Set of user-defined key-value pairs attached to the object. Partial updates are not supported. When updating, always submit whole metadata. Maximum of 64 parameters are allowed in the object.

service_account_idstring uuid

Identifier of the system-managed service account associated with this reader. Present only for readers that are already paired. This field is currently in beta and may change.

created_atstring date-time required

The timestamp of when the reader was created.

updated_atstring date-time required

The timestamp of when the reader was last updated.

Example response

{
  "id": "rdr_3MSAFM23CK82VSTT4BN6RWSQ65",
  "name": "Frontdesk",
  "status": "paired",
  "device": {
    "identifier": "U1DT3NA00-CN",
    "model": "solo"
  },
  "metadata": {},
  "created_at": "2023-01-18T15:16:17Z",
  "updated_at": "2023-01-20T15:16:17Z"
}