---
title: "2. Obtain the KeyId"
method: POST
path: "/authentication_keys"
---

# 2. Obtain the KeyId

`POST /authentication_keys`

## Headers

- `x-satispay-deviceinfo` string
- `x-satispay-devicetype` 'SMARTPHONE' | 'TABLET' | 'CASH REGISTER' | 'POS' | 'PC' | 'ECOMMERCE_PLUGIN'
- `x-satispay-os` string
- `x-satispay-osv` string
- `x-satispay-apph` string
- `x-satispay-appn` string
- `x-satispay-appv` string
- `x-satispay-tracking-code` string

## Request body

- object
  - `public_key` string, required — The `RSA` public key, in `PEM` format generated in the [previous step](https://developers.satispay.com/reference/generate-rsa-keys).
  - `token` string, required — The activation code required to authenticate the APIs. <br> <br> For more information read [here](https://developers.satispay.com/reference/keyid#how-the-token-field-works)

## Response `200`

OK

- object
  - `key_id` string — The KeyId generated for the activation code sent. <br> <br> The returned value must be saved in a safe place with the private and the public keys used.

## Other responses

- `400` — 400 Bad Request
- `403` — 403 Forbidden or invalid authorization header
- `404` — 404 Resource not found

---

[API](https://skmtc.net/satispay/apis/satispay-gbusiness-api.md) · [All operations](https://skmtc.net/satispay/apis/satispay-gbusiness-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/satispay/satispay-gbusiness-api/versions/f91f20a37e6f/schema)