cURL
curl --request POST \
--url https://api.slash.com/analytics \
--header 'Content-Type: application/json' \
--header 'X-API-Key: <api-key>' \
--data '
{
"query": "<string>"
}
'{
"columns": [
"<string>"
],
"rows": [
{}
],
"rowCount": 123,
"error": "<string>"
}Analytics
Query Analytics Data
Execute a SQL query against the user’s data.
The endpoint provides read-only access to secure views (transactions, cards, accounts, etc.) scoped to the authenticated user’s entities.
SQL Dialect: Uses Snowflake SQL syntax.
Data Freshness: Data may be up to 1 hour behind real-time.
Use SHOW TABLES to list available tables and DESCRIBE <table> to see columns.
POST
/
analytics
cURL
curl --request POST \
--url https://api.slash.com/analytics \
--header 'Content-Type: application/json' \
--header 'X-API-Key: <api-key>' \
--data '
{
"query": "<string>"
}
'{
"columns": [
"<string>"
],
"rows": [
{}
],
"rowCount": 123,
"error": "<string>"
}Authorizations
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.
Body
application/json
SQL query to execute
⌘I