---
title: "POST /user/{userID}/monetary-account/{monetary-accountID}/attachment"
method: POST
path: "/user/{userID}/monetary-account/{monetary-accountID}/attachment"
tags: ["attachment"]
---

# POST /user/{userID}/monetary-account/{monetary-accountID}/attachment

`POST /user/{userID}/monetary-account/{monetary-accountID}/attachment`

Create a new monetary account attachment. Create a POST request with a payload that contains the binary representation of the file, without any JSON wrapping. Make sure you define the MIME type (i.e. image/jpeg) in the Content-Type header. You are required to provide a description of the attachment using the X-Bunq-Attachment-Description header.

## Path parameters

- `userID` integer, required
- `monetary-accountID` 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

- AttachmentMonetaryAccount

## Response `200`

This call is used to upload an attachment that can be referenced to in payment requests and payments sent from a specific monetary account. Attachments supported are png, jpg and gif.

- AttachmentMonetaryAccountCreate
  - `id` integer — The ID of the attachment created.

## 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/versions/369477c7bd26/schema)