Appearance
Neteller
Neteller iGaming e-wallet via Paysafe — OAuth2 merchant deposits (transferIn), withdrawals (transferOut), customer lookup, and transaction status.
| Detail | Value |
|---|---|
| Category | iGaming |
| Base URL | https://api.neteller.com |
| Authentication | OAuth2 Client Credentials |
| Endpoints | 5 |
| Connector key | neteller |
Using Neteller in a workflow
- Go to Connections and click New Connection.
- Pick Neteller 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 |
|---|---|
POST /v1/oauth2/token | Obtain an OAuth2 access token (client_credentials) |
POST /v1/transferIn | Charge a Neteller customer (deposit) |
POST /v1/transferOut | Pay out to a Neteller customer (withdrawal) |
GET /v1/customers/{customerId} | Look up a Neteller customer by ID or email |
GET /v1/transactions/{transactionId} | Get a Neteller transaction by ID |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
POST /v1/oauth2/token
Obtain an OAuth2 access token (client_credentials)
| Detail | Value |
|---|---|
| Operation ID | getNetellerAccessToken |
| Method | POST |
| Path | /v1/oauth2/token |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
grant_type | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Neteller connection from the Connection dropdown.
- In the Operation dropdown, select
getNetellerAccessToken. - 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 Neteller API reference.
POST /v1/transferIn
Charge a Neteller customer (deposit)
| Detail | Value |
|---|---|
| Operation ID | createNetellerTransferIn |
| Method | POST |
| Path | /v1/transferIn |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
paymentMethod | object |
transaction | object |
verificationCode | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Neteller connection from the Connection dropdown.
- In the Operation dropdown, select
createNetellerTransferIn. - 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 Neteller API reference.
POST /v1/transferOut
Pay out to a Neteller customer (withdrawal)
| Detail | Value |
|---|---|
| Operation ID | createNetellerTransferOut |
| Method | POST |
| Path | /v1/transferOut |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
payeeProfile | object |
transaction | object |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Neteller connection from the Connection dropdown.
- In the Operation dropdown, select
createNetellerTransferOut. - 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 Neteller API reference.
GET /v1/customers/{customerId}
Look up a Neteller customer by ID or email
| Detail | Value |
|---|---|
| Operation ID | getNetellerCustomer |
| Method | GET |
| Path | /v1/customers/{customerId} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
customerId | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Neteller connection from the Connection dropdown.
- In the Operation dropdown, select
getNetellerCustomer. - 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 Neteller API reference.
GET /v1/transactions/{transactionId}
Get a Neteller transaction by ID
| Detail | Value |
|---|---|
| Operation ID | getNetellerTransaction |
| Method | GET |
| Path | /v1/transactions/{transactionId} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
transactionId | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Neteller connection from the Connection dropdown.
- In the Operation dropdown, select
getNetellerTransaction. - 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 Neteller API reference.