--- title: "Start noname card bulk process" method: POST path: "/cards/v1/bulks/{bulkID}/start" tags: ["Noname"] --- # Start noname card bulk process `POST /cards/v1/bulks/{bulkID}/start` Start noname card bulk/batch process. Each card is identified with an `external_id`. This endpoint starts the process begun with [Create noname card bulk](https://developers.pismo.io/pismo-docs/reference/create-bulk). Pass the bulk ID returned from that endpoint here. Each card created generates an event - [Card created](https://developers.pismo.io/events/docs/cards-create-1) - with event data that includes the card ID, bulk ID, and external ID. You pass the card ID to the [Associate noname card with customer](https://developers.pismo.io/pismo-docs/reference/post-v2-card-bind) endpoint. For more information on events and setting up event notifications, rerfer to the [Data and reporting](https://developers.pismo.io/pismo-docs/docs/data-reporting-overview) guide. For more information on embossing, refer to the [Physical card embossing](https://developers.pismo.io/pismo-docs/docs/physical-card-embossing) guide. For detailed information about embossing flows, refer to [Embossing flows](https://developers.pismo.io/pismo-docs/docs/physical-card-embossing#embossing-flows). ## Path parameters - `bulkID` string, required ## Response `202` Bulk was started and will be processed asynchronously - 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 ABU 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—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/revisions/935b62e16de4/schema)