cURL
curl --request GET \
--url https://api.slash.com/customer/{customerId}/ach-debit-recurring \
--header 'X-API-Key: <api-key>'{
"hasActiveRecurringAuth": true
}Customer
Check ACH debit recurring status
Check whether a customer has an active recurring ACH debit authorization. When active, the issuer can automatically debit the payer’s bank account for future invoices with auto-pull enabled.
GET
/
customer
/
{customerId}
/
ach-debit-recurring
cURL
curl --request GET \
--url https://api.slash.com/customer/{customerId}/ach-debit-recurring \
--header 'X-API-Key: <api-key>'{
"hasActiveRecurringAuth": true
}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.
Path Parameters
Query Parameters
The legal entity ID. Required if authenticating with access to multiple legal entities.
Response
OK
Whether the customer has authorized recurring ACH debits.
⌘I