Skip to main content

Changelog

Stay updated with the latest releases of the Dojo API.

This changelog highlights the latest and breaking changes in the Dojo API. Each new release version aligns with a date. This approach allows for a clear and chronological representation of our API versions, making it easier to track changes and updates over time.

info

If you want to integrate with the Dojo API for the first time or you want to upgrade from the previous version, contact us on Discord or GitHub.

2025-09-10​

Breaking changes​

  • Have to mandatorily pass 'Version' header with current API versions of '2025-09-10' and '2024-02-05'. Any other date in between these dates is also acceptable, and any date after 2025-09-10 is valid as well. The most recent version of the API that is before or exactly the date in the header will be used.
  • To prevent future modifications from becoming breaking changes for our users, we converted enums to strings in cases where we might add or remove fields. Enums that are unlikely to change or are essential for user-side logic have remained unchanged.

What's new?​

  • Introduced versioned APIs: the older spec resides in version 2024-02-05 and the newer one in version 2025-09-10.
  • When registering or fetching a new integration, capabilities are no longer an enum; they can be passed as a string.
  • When creating an event, eventType is no longer an enum; it can be passed as a string.
  • When creating a setup intent, merchantInitiatedTransactionType is no longer an enum; it can be passed as a string.
  • When creating a payment intent, paymentMethods is no longer an enum; it can be passed as a string.
  • When creating a session on terminal, notificationEvents is no longer an enum; it can be passed as a string.
  • When creating a payment intent, paymentDetails.card.entryMode is no longer an enum; it can be passed as a string.
  • When creating a payment intent, paymentDetails.card.verificationMethod is no longer an enum; it can be passed as a string.
  • When creating a payment intent, merchantConfig.supportedPaymentMethods.cardSchemes and merchantConfig.supportedPaymentMethods.wallets are no longer enums; they can be passed as string.

API reference Learn about the API and integrate with API endpoints.

Support Our support team is always happy to help with any questions you have.

Last updated on