Back to neotek ↗Get Sandbox Access

ListProfileScheduledPayments

GEThttps://test.api.neotek.sa/single-api-aggregator/v1/profile/scheduled-payments/{account_id}

Sandbox URL · in Production call https://api.neotek.sa

Returns the payments the customer has scheduled from an account — future-dated transfers they have set up in advance but that have not executed yet.

Path parameters:

ParameterRequiredDescription
account_idRequiredthe account to look up, an AccountId from ListProfileAccounts

Query parameters:

ParameterRequiredDescription
psu_idOptionalthe Payment Service User id: the identifier you assign to the customer in your own system. Use the same id you sent when creating the accounts link, since that is how Neotek resolves which consented accounts to return

Headers:

ParameterRequiredDescription
authorizationRequiredBearer <ACCESS_TOKEN>, with scope single_api
x-request-idOptionalan RFC 4122 UUID you generate; quote it when raising a support ticket
cURL
curl 'https://test.api.neotek.sa/single-api-aggregator/v1/profile/scheduled-payments/{account_id}' \  -H 'Authorization: Bearer <ACCESS_TOKEN>'

Response (schema — ScheduledPayment is a list of payment references, and Meta carries only TotalPages)

JSON
{    "Data": {        "AccountId": "string",        "ScheduledPayment": [            "string"        ]    },    "Links": {        "Self": "string",        "First": "string",        "Last": "string"    },    "Meta": {        "TotalPages": 0    }}

Errors

ScenarioStatusCodeMessage
Missing required param400NTSP.ERROR.400.090One or more required API parameters are missing in the API request.
Invalid enum value400NTSP.ERROR.400.901Backend Invalid Request Body
Invalid/expired token401NTSP.ERROR.401.001Cannot pass the security checks that are required by the target API or operation…
No Authorization header401NTSP.ERROR.401.001Invalid client id or secret.
Wrong method405nullThe method is not allowed for the requested URL