---
title: "Create a Reader"
method: POST
path: "/v0.1/merchants/{merchant_code}/readers"
tags: ["Readers"]
---

# Create a Reader

`POST /v0.1/merchants/{merchant_code}/readers`

Create a new Reader for the merchant account.

## Path parameters

- `merchant_code` string, required

## Request body

- object
  - `pairing_code` string, 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.
  - `name` string, required — Custom human-readable, user-defined name for easier identification of the reader.
  - `meta` Meta — A set of key-value pairs that you can attach to an object. This can be useful for storing additional information about the object in a structured format. **Warning**: Updating Meta will overwrite the existing data. Make sure to always include the complete JSON object.

## Response `201`

Returns the Reader object if the creation succeeded.

- Reader — A physical card reader device that can accept in-person payments.
  - `id` string, required — Unique identifier of the object. Note that this identifies the instance of the physical devices pairing with your SumUp account. If you DELETE a reader, and pair the device again, the ID will be different. Do not use this ID to refer to a physical device.
  - `name` string, 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.
  - `device` ReaderDevice, required — Information about the underlying physical device.
    - `identifier` string, required — A unique identifier of the physical device (e.g. serial number).
    - `model` 'solo' | 'virtual-solo', required — Identifier of the model of the device.
  - `meta` Meta — A set of key-value pairs that you can attach to an object. This can be useful for storing additional information about the object in a structured format. **Warning**: Updating Meta will overwrite the existing data. Make sure to always include the complete JSON object.
  - `created_at` string, date-time, required — The timestamp of when the reader was created.
  - `updated_at` string, date-time, required — The timestamp of when the reader was last updated.

## Changes

- **2025-10-29** `4dc4b073a6a9` — 3 breaking
  - the request property `name` became required
  - the `meta/additionalProperties/` request property type changed from no type to `string`
  - the `meta/additionalProperties/` response's property type changed from no type to `string` for status `201`
- **2025-03-26** `80a17713e7a8` — 1 info
  - the security scope `readers.write` was added to the endpoint's security scheme `oauth2`
- **2025-02-25** `cdadac3315a1` — 2 info
  - the endpoint scheme security `apiKey` was added to the API
  - the endpoint scheme security `oauth2` was added to the API

[Change history](https://skmtc.dev/sumup/apis/sumup-rest-api/changes/v0.1/merchants/:merchant_code/readers/post.md)

---

[API](https://skmtc.dev/sumup/apis/sumup-rest-api.md) · [All operations](https://skmtc.dev/sumup/apis/sumup-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/sumup/sumup-rest-api/revisions/d32eef8a3bd2/schema)