Shift4

Payment processing for iGaming with charges, refunds, customer management, and subscriptions.

Detail	Value
Category	iGaming
Base URL	https://api.shift4.com
Authentication	Bearer Token
Endpoints	10
Connector key	shift4

Using Shift4 in a workflow

1. Go to Connections and click New Connection.
2. Pick Shift4 from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
POST /charges	Create charge
GET /charges/{charge_id}	Get charge
POST /charges/{charge_id}/capture	Capture charge
POST /refunds	Create refund
GET /refunds/{refund_id}	Get refund
POST /customers	Create customer
GET /customers/{customer_id}	Get customer
POST /customers/{customer_id}/cards	Add card
GET /customers/{customer_id}/cards	List cards
POST /subscriptions	Create subscription

Each endpoint is documented in full below. Use the outline on the right to jump to one.

POST /charges

Create charge

Detail	Value
Operation ID	igaming.createCharge
Method	POST
Path	/charges

Parameters

No parameters.

Request Body

Field	Type
amount	integer
currency	string
card	object

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.createCharge.
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 {{nodeId.data.path}}. The exact response shape is documented on the upstream Shift4 API reference.

GET /charges/{charge_id}

Get charge

Detail	Value
Operation ID	igaming.getCharge
Method	GET
Path	/charges/{charge_id}

Parameters

Name	Location	Type	Required
charge_id	path	string	Yes

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.getCharge.
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 {{nodeId.data.path}}. The exact response shape is documented on the upstream Shift4 API reference.

POST /charges/{charge_id}/capture

Capture charge

Detail	Value
Operation ID	igaming.captureCharge
Method	POST
Path	/charges/{charge_id}/capture

Parameters

Name	Location	Type	Required
charge_id	path	string	Yes

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.captureCharge.
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 {{nodeId.data.path}}. The exact response shape is documented on the upstream Shift4 API reference.

POST /refunds

Create refund

Detail	Value
Operation ID	igaming.createRefund
Method	POST
Path	/refunds

Parameters

No parameters.

Request Body

Field	Type
chargeId	string
amount	integer

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.createRefund.
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 {{nodeId.data.path}}. The exact response shape is documented on the upstream Shift4 API reference.

GET /refunds/{refund_id}

Get refund

Detail	Value
Operation ID	igaming.getRefund
Method	GET
Path	/refunds/{refund_id}

Parameters

Name	Location	Type	Required
refund_id	path	string	Yes

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.getRefund.
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 {{nodeId.data.path}}. The exact response shape is documented on the upstream Shift4 API reference.

POST /customers

Create customer

Detail	Value
Operation ID	igaming.createCustomer
Method	POST
Path	/customers

Parameters

No parameters.

Request Body

Field	Type
email	string
description	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.createCustomer.
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 {{nodeId.data.path}}. The exact response shape is documented on the upstream Shift4 API reference.

GET /customers/{customer_id}

Get customer

Detail	Value
Operation ID	igaming.getCustomer
Method	GET
Path	/customers/{customer_id}

Parameters

Name	Location	Type	Required
customer_id	path	string	Yes

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.getCustomer.
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 {{nodeId.data.path}}. The exact response shape is documented on the upstream Shift4 API reference.

POST /customers/{customer_id}/cards

Add card

Detail	Value
Operation ID	igaming.addCard
Method	POST
Path	/customers/{customer_id}/cards

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 {{nodeId.data.path}}. The exact response shape is documented on the upstream Shift4 API reference.

GET /customers/{customer_id}/cards

List cards

Detail	Value
Operation ID	igaming.listCards
Method	GET
Path	/customers/{customer_id}/cards

Parameters

Name	Location	Type	Required
customer_id	path	string	Yes

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.listCards.
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 {{nodeId.data.path}}. The exact response shape is documented on the upstream Shift4 API reference.

POST /subscriptions

Create subscription

Detail	Value
Operation ID	igaming.createSubscription
Method	POST
Path	/subscriptions

Parameters

No parameters.

Request Body

Field	Type
customerId	string
planId	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.createSubscription.
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 {{nodeId.data.path}}. The exact response shape is documented on the upstream Shift4 API reference.