---
title: "Create a new card type"
method: POST
path: "/card-types"
tags: ["Card types"]
---

# Create a new card type

`POST /card-types`

Create a new card type. Card types define the categories of cards that can be issued to customers, including the name and the prefix applied to card numbers of that type.

## Headers

- `Accept-Language` string

## Request body

- object
  - `card_type` CardType, required — CardType resource.
    - `card_type_id` string — The unique ID of the card type.
    - `text_id` string — The unique text identifier of the card type.
    - `name` string, required — Name of the card type.
    - `prefix` string, required — Prefix of the specific card type cards.

## Response `201`

Created

- object
  - `data` object
    - `card_type_id` string — The unique ID of the card type.

## Other responses

- `400` — Bad input parameter. The response body's `error.error_data.invalid_params[]` array lists the parameters that caused the failure, each carrying a `reason` code. See the `BadRequestErrorBody` schema for the generic reason taxonomy. Operations with domain-specific business rules document additional reasons at the operation level.
- `401` — The client has invalid credentials or auth token.
- `403` — The client does not exist or the client tried to access an unauthorized property or resource.
- `404` — The resource was not found.
- `405` — The resource does not support the specified HTTP method.
- `429` — Too many requests - more than the resource limit.
- `500` — Server is not working as expected.
- `503` — Temporary state when the service is temporarily unavailable, overloaded or there is a maintenance window.

---

[API](https://skmtc.net/crmcarecloud/apis/rest-api-reference.md) · [All operations](https://skmtc.net/crmcarecloud/apis/rest-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/crmcarecloud/rest-api-reference/revisions/329c06dbf8d9/schema)