cURL
curl --request GET \
--url https://api.slash.com/account \
--header 'X-API-Key: <api-key>'{
"items": [
{
"id": "<string>",
"name": "<string>",
"accountNumber": "<string>",
"routingNumber": "<string>",
"createdAt": "2023-11-07T05:31:56Z",
"balances": []
}
],
"metadata": {
"nextCursor": "<string>",
"count": 123
}
}Account
List accounts
List all accounts you have access to
GET
/
account
cURL
curl --request GET \
--url https://api.slash.com/account \
--header 'X-API-Key: <api-key>'{
"items": [
{
"id": "<string>",
"name": "<string>",
"accountNumber": "<string>",
"routingNumber": "<string>",
"createdAt": "2023-11-07T05:31:56Z",
"balances": []
}
],
"metadata": {
"nextCursor": "<string>",
"count": 123
}
}Documentation Index
Fetch the complete documentation index at: https://docs.slash.com/llms.txt
Use this file to discover all available pages before exploring further.
Authorizations
api_keybearer
API key authentication for public API requests.
Keys come in two flavors:
- Legal-entity-scoped keys are pinned to a single legal entity. Minted via the dashboard under a specific entity; every request acts on that entity.
- User-scoped keys are pinned to a user and span every legal
entity that user has access to. Every request made with a
user-scoped key (except
GET /legal-entity, which lists the legal entities the user can access) must include anx-legal-entityheader naming the legal entity the request is operating on. Requests without the header are rejected with400. The authenticated user must have an active permission role on the supplied legal entity, otherwise the request is rejected with403.
Query Parameters
Pass in a legal entity ID to filter for accounts under a specific legal entity.
⌘I