​
2025-06-10

  • Added /account/{accountId}/authorization-webhook endpoint. This endpoint allows you to retrieve, create, and update the authorization webhook for an account. This is only an enterprise feature; reach out to sales@slash.com to request access.

​
2025-06-05

  • Added wireInfo and achInfo to the Transaction object

​
2025-05-17

  • Added required name field to the Account schema.

​
2025-05-09

  • Added virtualAccountId to the card group object.
  • Added virtualAccountId as an optional parameter to the POST /card-group request body.

​
2025-02-06

  • Added GET /card/{cardId}/utilization endpoint. This endpoint allows you get the utilization for a single card not associated with a card group.

​
2025-02-05

  • Added POST /virtual-account/transfer. This endpoint allows you to transfer funds between virtual accounts.

​
2025-01-31

  • Added transactions visible only on transactions page to GET /transaction and GET /transaction/aggregation
  • Currently, these types of transactions are limited to transfers between virtual accounts

​
2025-01-28

  • Added filter:cardGroupName to GET /card endpoint. This field allows you to filter cards by card group name.

​
2025-01-23

  • Added filter:name to GET /card-group endpoint. This field allows you to filter card groups by name.
  • Added memo field to GET /transaction endpoint. This field contains the memo field for ach transactions and the sender reference for wire transactions.

​
2025-01-19

  • Added PATCH /card/{cardId}/spending-constraint and PATCH /card-group/{cardGroupId}/spending-constraint endpoints. These endpoints allow for partial updating of existing spending constraints while preserving original values.
  • For consistency, added PUT /card/{cardId}/spending-constraint and PUT /card-group/{cardGroupId}/spending-constraint endpoints. These endpoints fully replace the existing spending constraint with the new one.

​
2024-12-05

  • Added GET /card-product endpoint for getting card product information.
  • Added cardProductId field to POST /card endpoint for creating a card with a specific card product.

​
2024-12-05

  • Added GET /transaction/aggregation endpoint for getting aggregated statistics about transactions.

​
2024-12-03

  • Added virtualAccountId field to card creation request and response. accountId is still required, while this field is optional.

​
2024-11-30

  • Added merchantData field to Transaction. This field allows you to read specific details about the merchant, such as its reported description of the transaction, category code and location. Only applicable for card transactions.
  • Deprecated merchantDescription field in Transaction in favor of merchantData.description

​
2024-11-28

  • Added Virtual Account endpoints to the API, allowing you to view, update, and close them

​
2024-10-20

  • Added sort query param to the GET /card endpoint. This field allows you to sort cards by creation date or name.
  • Added sortDirection query param to the GET /card endpoint. This field allows you to control the direction of the sort.

​
2024-10-03

  • Added cardGroupId field to card creation request
  • Added GET /card-group/{cardGroupId}/utilization endpoint. This endpoint returns the current utilization for a card group.

​
2024-07-10

  • Added referenceNumber field to Transaction schema, which is returned by the GET /transaction and GET /transaction/{transactionId} endpoints.

​
2024-07-02

  • Added filter:detailed_status query param to the GET /transaction endpoint. This field allows you to filter transactions by their detailed status. See the API reference for more details.

​
2024-06-25

  • Added GET /card/{cardId}/events endpoint. This endpoint returns events from Visa for a single card, including authorizations, reversals, and verifications. See the API reference for more details.

​
2024-06-20

  • Added userData field to the POST /card and PATCH /card/{cardId} requests. This field allows you to attach your own data to the card, like an email address or an internal ID.
  • Added detailedStatus and declineReason fields to the Transaction schema, which is returned by the GET /transaction and GET /transaction/{transactionId} endpoints.

​
2024-06-14

  • Added PATCH /transaction/{transactionId}/note endpoint. This endpoint allows you to add a note to a transaction. See the API reference for more details.

​
2024-05-01

We’ve made a number of non-breaking changes to the API. For the most part, you can continue to use the API as you have been, as long as you’ve been authenticating via API key. Here’s what’s new:
  • Added /legal-entity endpoint. This endpoint returns the legal entities available to you. You can use this to filter the results of other endpoints.
  • Added optional filter:legalEntityId query params to the following endpoints. This field allows you to specify the legal entity to filter by. If you are authenticating with an API key, this field will default to the legal entity the API key is associated with. If you are authenticating with a user token, you can use this field to filter by legal entity.
    • GET /account
    • GET /transaction
    • GET /card
    • GET /webhook
  • Added optional filter:accountId query params to the following endpoints. This field allows you to specify the account to filter by.
    • GET /card
  • Renamed the PayBySlashUser schema to SlashHandle.
  • Renamed the sourceSlashAccountGroup field in SlashHandle to accountId, which represents the ID of the account that will be used to send and receive funds.
    • Note that this is a breaking change. If you are relying on this field, please update your code to use the new field name.
  • Added GET /slash-handle. The GET /pay endpoint will continue to work, but we recommend updating your code to use the new endpoint, which returns a list instead of a single Slash handle (although the list will usually only contain one element).
  • Added optional sourceSlashHandleId and legalEntityId fields to the POST /pay request body. This field allows you to specify the legal entity or slash handle to use for the payment. (Each legal entity has one Slash handle.) If you are authenticating with an API key, this field will default to your legal entity’s Slash handle. If you are authenticating with a user token, one of these fields is required.
  • Added optional legalEntityId field to the POST /webhook request body. This field allows you to specify the legal entity to create the webhook for. If you are authenticating with an API key, this field will default to your legal entity. If you are authenticating with a user token, this field is required.
  • Added optional accountId field to the POST /card request body. This field allows you to specify the account to create the card for. If you are authenticating with an API key, this field will default to the first commercial account under your legal entity, but we recommend that you specify the account ID explicitly. If you are authenticating with a user token, this field is required.