Afterpay

undefined

Detail	Value
Category	Finance
Base URL	https://global-api.afterpay.com/v2
Authentication	API Key
Endpoints	5
Connector key	afterpay

Using Afterpay in a workflow

1. Go to Connections and click New Connection.
2. Pick Afterpay 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
GET	Checkouts
GET	Payments
GET	Capture
GET	Refunds
GET	Configuration

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

GET

Checkouts

Detail	Value
Operation ID	checkouts_0
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

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

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 Afterpay API reference.

GET

Payments

Detail	Value
Operation ID	payments_1
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

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

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 Afterpay API reference.

GET

Capture

Detail	Value
Operation ID	capture_2
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

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

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 Afterpay API reference.

GET

Refunds

Detail	Value
Operation ID	refunds_3
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

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

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 Afterpay API reference.

GET

Configuration

Detail	Value
Operation ID	configuration_4
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

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

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 Afterpay API reference.