---
title: 'POST /customers/{customer_id}/cards'
description: 'Add card'
---

# POST /customers/{customer_id}/cards

Add card

| Detail | Value |
|---|---|
| Operation ID | `igaming.addCard` |
| Method | `POST` |
| Path | `/customers/{customer_id}/cards` |
| Connector | [Shift4](./) |

## Parameters

| Name | Location | Type | Required |
|---|---|---|---|
| `customer_id` | path | string | **Yes** |

## Request Body

| Field | Type |
|---|---|
| `number` | string |
| `expMonth` | string |
| `expYear` | string |
| `cvc` | string |


## Using this endpoint in a workflow

1. Add an **API Call** node to your workflow.
2. Pick your Shift4 connection from the Connection dropdown.
3. In the Operation dropdown, select `igaming.addCard`.
4. Fill in the parameter fields that appear. Use `{{...}}` to reference upstream values.

**Required fields are marked — fill them or the call will fail at runtime.**

## What it returns

The `API Call` node writes the response to the workflow context:

```
{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}
```

Reference response fields downstream as <code v-pre>{{nodeId.data.path}}</code>. The exact response shape is documented on the upstream Shift4 API reference.