cURL
curl --request PUT \
--url https://api.slash.com/card/{cardId}/modifier \
--header 'Content-Type: application/json' \
--header 'X-API-Key: <api-key>' \
--data '{
"value": true
}'{
"success": true
}Card
Set card modifier
Set a modifier for a card.
PUT
/
card
/
{cardId}
/
modifier
cURL
curl --request PUT \
--url https://api.slash.com/card/{cardId}/modifier \
--header 'Content-Type: application/json' \
--header 'X-API-Key: <api-key>' \
--data '{
"value": true
}'{
"success": true
}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.
Enterprise Feature: Card modifiers are an enterprise-only feature. Please reach out to sales@slash.com to get set up with this functionality.
Usage Examples
Enable recurring payments only
{
"name": "only_allow_recurring_payments",
"value": true
}
Disable recurring payments restriction
{
"name": "only_allow_recurring_payments",
"value": false
}
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
Body
application/json
Response
OK
⌘I