---
title: "POST /user/{userID}/certificate-pinned"
method: POST
path: "/user/{userID}/certificate-pinned"
tags: ["certificate-pinned"]
---

# POST /user/{userID}/certificate-pinned

`POST /user/{userID}/certificate-pinned`

Pin the certificate chain.

## Path parameters

- `userID` integer, required

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

- CertificatePinned
  - `certificate_chain` Certificate[], required — The certificate chain in .PEM format.
    - `certificate` string — A single certificate in the chain in .PEM format.

## Response `200`

This endpoint allow you to pin the certificate chains to your account. These certificate chains are used for SSL validation whenever a callback is initiated to one of your https callback urls.

- CertificatePinnedCreate
  - `id` integer — The id generated for the pinned certificate chain.

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