API version reference
Moov's API versioning follows the format vYYYY.QQ.BB, where
YYYYis the yearQQis the two-digit month for the first month of the quarter (e.g.,01,04,07,10)BBis the build number, starting at.00, for subsequent builds in the same quarter.
For example, v2025.01.00 is the initial release of the first quarter of 2025.
When an API version is released at the start of a new quarter, it's considered in beta. When the quarter ends, it moves to stable. For example, in July of 2026, v2026.07.00 will be released as a beta version. In October, when v2026.10.00 is released in beta, v2026.07.00 will move to stable. Note, the previous quarter's API version will become stable at the start of the next quarter, even if a new API version is not released.
v2024.01.00.
Available versions
latest(latest is always considered in beta)v2025.07.00v2025.04.00v2025.01.00v2024.01.00(default)
2025.07.00
- New support tickets allow you to hand off connected account support to Moov, and Moov will respond
- Granular capabilities allow you to only request the capabilities you need, shortening onboarding time
- Underwriting dynamically generates based on an account's business profile and requested capabilities
- New enriched industry taxonomies model
- Allows Moov to create guest accounts for Tap to Pay processing
2025.04.00
- Added support for a
terminalCardsource and thecard-present-paymentpayment method type for in-person payments.
2025.01.00
- Updated error response status codes.
latest (beta)
Moov's latest API version will have our newest features and updates. The latest version is always considered in beta. Browse the changelog for announcements or browse the API site.
Breaking changes
- Non-breaking changes may be added to a release even after it becomes stable.
- Minor breaking changes may be added to a release while it's in beta. Moov attempts to minimize this as much as possible.
- Brand new features or major breaking changes will be in API version
latest. Moov may release new features or major breaking changes for customers who are in specific beta programs or testing various features with us.
See the breaking changes guide for more details.
SDK versioning
Because our SDKs are generated from the latest specification, setting the API version to latest when instantiating an API client will have the best results.