---
title: "GET /user/{userID}/card-name"
method: GET
path: "/user/{userID}/card-name"
tags: ["card-name"]
---

# GET /user/{userID}/card-name

`GET /user/{userID}/card-name`

Return all the accepted card names for a specific user.

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

## Response `200`

Endpoint for getting all the accepted card names for a user. As bunq do not allow total freedom in choosing the name that is going to be printed on the card, the following formats are accepted: Name Surname, N. Surname, N Surname or Surname.

- CardNameListing[]
  - `possible_card_name_array` string[] — All possible variations (of suitable length) of user's legal name for the debit card.

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