---
title: "Increment noname card bulk"
method: PUT
path: "/cards/v1/bulks/{bulkID}"
tags: ["Noname"]
---

# Increment noname card bulk

`PUT /cards/v1/bulks/{bulkID}`

Increment noname card bulk/batch with up to 1000 additional cards.
Use the bulk ID returned from [Create noname card bulk](https://developers.pismo.io/pismo-docs/reference/create-bulk).

One card is created for each `external_id` entered.

## Path parameters

- `bulkID` string, required

## Request body

- IncrementBulk — Increment noname card bulk request object
  - `external_ids` string[], required — Client assigned IDs for internal tracking purposes. One card is created for each ID. The maximum number of cards in one bulk/batch is 1000. If you want to use more than 36 characters for your external IDs, please request a change in the embossing layout via a Jira ticket. By default, an embossing layout supports 36 digits for external IDs.

## Response `201`

Bulk was incremented

- BulkResponse
  - `abu_enabled` boolean — This field is **DEPRECATED**. For more information, refer to the [ABU documentation](https://developers.pismo.io/pismo-docs/docs/cards-overview-1#mastercards-automatic-billing-updater-option) in the Cards overview guide. When a card is created or reissued, or its account credentials change, Mastercard is notified if this feaure is enabled. Notification updates are sent to Mastercard on a daily basis. For more information, refer to Mastercard's <a href="https://developer.mastercard.com/product/automatic-billing-updater-abu/" target="_blank">ABU</a> documentation.
  - `contactless_enabled` boolean — For physical cards. Is card enabled for contactless transactions? With contactless transactions, you hold or tap the card on contactless-enabled card reader to complete a transaction. This requires that both the card and the terminal have Near Field Communication (NFC) technology. Most embossers can create plastic contactless cards. Default is `true`.
  - `embossing_custom_field` string — For physical cards. Additional information for embossing company. For example: tracking number or whether the card should be plastic or metal. You can use this field for any embossing needs specific to your business. Whatever is sent must be agreed upon with the embosser&mdash;what to send, what values to send, what format to send, what size to send for each value, and so on.
  - `id` string — Bulk ID.
  - `metadata` string — Any data object with key/value pairs. No limit on length. **Note**: This field must not be used to send Personally Identifiable Information (PII), Payment Card Industry (PCI) data, or any sensitive/regulated information. Metadata fields are intended for operational, non-sensitive data only. For sensitive data, use the specific parameters designed for that purpose. For more information, refer to [Get started with Pismo APIs](https://developers.pismo.io/pismo-docs/reference/get-started-with-pismo-apis#metadata).
  - `program_id` number — Pismo program ID.
  - `template_id` string — Template ID. Templates are used to implement the BIN override feature. For more information, refer to the [BIN override](https://developers.pismo.io/pismo-docs/docs/bin-override-feature) guide.
  - `size` integer — Bulk size - number of cards
  - `status` 'CREATED' | 'RUNNING' | 'COMPLETED' — Bulk noname card job status.
  - `validity_period_hours` integer — How long, in hours, the card is valid. Cannot exceed the card's `expiration_date`. Once this period is exceeded, and the card has a `NORMAL`, `BLOCKED`, `PENDING`, `WARNING` or `REISSUED` status, its status becomes `INOPERATIVE`. This field is used to calculate the datetime value for `valid_until`. For `VIRTUAL` and `PLASTIC` cards. Setting this field for `TEMPORARY` or `RECURRING` cards returns a **400 Bad request** error.

## Other responses

- `400` — Bad request
- `404` — Not Found
- `409` — The specified resource status conflicts with the current request.
- `500` — Internal server error

---

[API](https://skmtc.net/pismo/apis/platform-authentication.md) · [All operations](https://skmtc.net/pismo/apis/platform-authentication/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pismo/platform-authentication/versions/935b62e16de4/schema)