Appearance
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
- Go to Connections and click New Connection.
- Pick Afterpay from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- 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
- Add an API Call node to your workflow.
- Pick your Afterpay connection from the Connection dropdown.
- In the Operation dropdown, select
checkouts_0. - 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
- Add an API Call node to your workflow.
- Pick your Afterpay connection from the Connection dropdown.
- In the Operation dropdown, select
payments_1. - 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
- Add an API Call node to your workflow.
- Pick your Afterpay connection from the Connection dropdown.
- In the Operation dropdown, select
capture_2. - 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
- Add an API Call node to your workflow.
- Pick your Afterpay connection from the Connection dropdown.
- In the Operation dropdown, select
refunds_3. - 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
- Add an API Call node to your workflow.
- Pick your Afterpay connection from the Connection dropdown.
- In the Operation dropdown, select
configuration_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.