👍

Don't miss new announcements

Check out how to get notified of new changes in your favorite messaging application:

Our RSS Feed

• Slack: link
• Microsoft Teams: link

We are thrilled to make an experimental version of webhooks available for evaluation! Request access to this experimental feature to your CSM, subscribe to one or more events and start receiving API calls for them! Read more in this guide.
We look forward to your feedback in our mailbox!

It is now possible to request payables modified after a given date - simply use the updatedFrom parameter. See an example below:

🚧

Breaking Changes

When going through multiple pages of results in all paginated endpoints, it was possible to provide any page number and receive an HTTP 200 response with an empty collection through the page query parameter.

As of now, whenever a page other than the first that does not yield results (therefore doesn't exist) is requested, our system will respond with 404.

We are excited to announce experimental endpoints that allow you to retrieve your purchase- and bank- journals. Just like in the Spendesk UI, you can now retrieve your purchase- and bank-journals in CSV format via APIs.
This is an experimental version that has passed our internal testing but requires extensive validation by customers. Please let us know if you are interested in testing it by reaching out to us at [email protected].

👍

New date filter for settlements

We are happy to announce that it is now possible to request settlements with a date range! Use these new query parameters - clearedFrom and clearedTo like so:

cURL

curl --request GET \
     --url 'https://public-api.demo.spendesk.com/v1/settlements?clearedFrom=2024-01-01&clearedTo=2024-01-31' \
     --header 'accept: application/json'

Clearing date is the date retained by Spendesk when processing various types of settlements.

🚧

Breaking Changes

The OAuth2 Refresh Token POST endpoint now supports two new mandatory query parameters:

• client_id - The original Client ID received by Spendesk
• client_secret - The original Client Secret received by Spendesk

These two new parameters are needed for us to successfully rotate your access and refresh tokens in a more secure fashion. Without them, the request will result in a response with the status code 400.

In addition to the breaking changes announced above, the OAuth2 Refresh Token POST endpoint also now returns a new property:

• refresh_token - The new refresh token to be used from then on out

This new refresh token will invalidate the previously returned one in the OAuth2 Access Token POST endpoint, and has a validation period 30 days.

🚧

Last warning!

Endpoints under the v0 path will no longer be accessible from Mon April 29th. Any call to /v0 endpoints will result in a 404.

This is a call to action to immediately update your code to use v1 endpoints! Access and refresh tokens obtained using /v0 endpoints can be reused with /v1 endpoints.

👍

We are happy to release the first stable version of the Spendesk API with a long term support commitment!

Check out the Introduction section for more details on requesting access and the use cases supported by Spendesk APIs.

Here is the list of notable changes compared to v0:

• The synchronous endpoint to retrieve payables has been removed in favor of the asynchronous one Create a snapshot of payables
• The range to retrieve payables by payableDate is now limited to 31 days, so the time between fromPayableDate and toPayableDate should not exceed 31 days.
• The maximum page size across all endpoints is now 30.

Please note that v0 endpoints will no longer be functional as of Apr 29th, 2024. This is a call to action to update your integrations with the new path.

🚧

Breaking changes on Mar 14, 2024

Please note that we have introduced two breaking changes today:

• The range to retrieve payables by payableDate is now limited to 31 days, so the time between fromPayableDate and toPayableDate should not exceed 31 days.
• The maximum page size across all endpoints is now 30.