---
title: "POST /installation"
method: POST
path: "/installation"
tags: ["installation"]
---

# POST /installation

`POST /installation`

This is the only API call that does not require you to use the "X-Bunq-Client-Authentication" and "X-Bunq-Client-Signature" headers.
 You provide the server with the public part of the key pair that you are going to use to create the value of the signature header for all future API calls. The server creates an installation for you. Store the Installation Token and ServerPublicKey from the response. This token is used in the "X-Bunq-Client-Authentication" header for the creation of a DeviceServer and SessionServer.

## Headers

- `Cache-Control` string
- `User-Agent` string, required
- `X-Bunq-Language` string
- `X-Bunq-Region` string
- `X-Bunq-Client-Request-Id` string
- `X-Bunq-Geolocation` string
- `X-Bunq-Client-Authentication` string, required

## Request body

- Installation
  - `client_public_key` string, required — Your public key. This is the public part of the key pair that you are going to use to create value of the "X-Bunq-Client-Signature" header for all future API calls.

## Response `200`

Installation is used to tell the server about the public key of your key pair. The server uses this key to verify your subsequent calls, which need to be signed with your own private key. Additionally, you can use the token you get from an Installation to authenticate the registration of a new device.

- InstallationCreate
  - `Id` BunqId
    - `id` integer — An integer ID of an object. Unique per object type.
  - `Token` InstallationToken
    - `id` integer — The id of the Token.
    - `created` string — The timestamp of the Token's creation.
    - `updated` string — The timestamp of the Token's last update.
    - `token` string — The installation token is the token the client has to provide in the "X-Bunq-Client-Authentication" header for the creation of a DeviceServer and SessionServer.
  - `ServerPublicKey` InstallationServerPublicKey
    - `server_public_key` string — The server's public key for this Installation. You should use this key to verify the "X-Bunq-Server-Signature" header for each response from the server.

## Other responses

- `400` — This is how the error response looks like for 4XX response codes

---

[API](https://skmtc.net/bunq/apis/bunq-api.md) · [All operations](https://skmtc.net/bunq/apis/bunq-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/bunq/bunq-api/revisions/369477c7bd26/schema)