---
title: "POST /device-server"
method: POST
path: "/device-server"
tags: ["device-server"]
---

# POST /device-server

`POST /device-server`

Create a new DeviceServer providing the installation token in the header and signing the request with the private part of the key you used to create the installation. The API Key that you are using will be bound to the IP address of the DeviceServer which you have created.<br/><br/>Using a Wildcard API Key gives you the freedom to make API calls even if the IP address has changed after the POST device-server.<br/><br/>Find out more at this link <a href="https:/bunq.com/en/apikey-dynamic-ip" target="_blank">https:/bunq.com/en/apikey-dynamic-ip</a>.

## 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

- DeviceServer
  - `description` string, required — The description of the DeviceServer. This is only for your own reference when reading the DeviceServer again.
  - `secret` string, required — The API key. You can request an API key in the bunq app.
  - `permitted_ips` string[] — An array of IPs (v4 or v6) this DeviceServer will be able to do calls from. These will be linked to the API key.

## Response `200`

After having created an Installation you can now create a DeviceServer. A DeviceServer is needed to do a login call with session-server.

- DeviceServerCreate
  - `id` integer — The id of the DeviceServer as created on 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)