Request a card
Ask for a card for yourself. An approver decides in Slash.
Authorizations
User API key authentication. Create a key under Settings → API keys in the Slash dashboard (https://app.slash.com/global-settings/api-keys) and send the x-legal-entity header naming the legal entity to act on with every request. Keys scoped to a legal entity are rejected with 403 user_api_key_required.
Headers
Unique caller-generated key for one create request. Once an authenticated, schema-valid request reaches the operation, the key is permanently consumed for that operation and legal entity whether the operation succeeds or fails. Reusing it in that scope returns 409 and never replays a response, unlike API v1, which replays the original response for a matching key.
1 - 255The legal entity to act on. Required on every request; a user API key can act on any legal entity its user has access to.
^le_[a-zA-Z0-9]+$Body
- CardRequestCreateVirtual
- CardRequestCreatePhysical
virtual 1 - 255The account to request the card on. Required when the legal entity has more than one card account.
Defaults to the account's primary virtual account.
1000Response
The card request.
A request for a card that an approver decides on in Slash.
Card request id with the card_request_ prefix.
"card_request_2rj4l7hmrrrcv"
approved requests issue their card shortly after; cardId is set once it exists.
pending, approved, rejected, canceled, expired virtual, physical "Ads – Meta"
"sa_group_2rj4l7hmrrrcv"
"u_2rj4l7hmrrrcv"
"subaccount_2rj4l7hmrrrcv"
"card_group_2rj4l7hmrrrcv"
The card issued for the request.
"c_2rj4l7hmrrrcv"