GET /api/v2/{}/subscription_templates/{}/checkout_identifier* → endpoint removal
Moneybird API
Deprecated, no date
Moneybird has deprecated the endpoint GET /api/v2/{}/subscription_templates/{}/checkout_identifier* without a shutdown date. Calls made to this route are slated to fail once it is removed.
Calls it hits
GET /api/v2/{}/subscription_templates/{}/checkout_identifier*
What to use instead of these calls
Create an online sales link with POST /api/v2/{administration_id}/subscription_templates/{id}/sales_link instead.
In Moneybird API's words
GET /{administration_id}/subscription_templates/{id}/checkout_identifier{format} - endpoint deprecated
Facts
- API
- Moneybird API
moneybird.com - Kind
- Endpoint removal
- Announced
- October 7, 2025
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Moneybird API's own pages
Questions
When does this change take effect?
Moneybird API deprecated GET /api/v2/{}/subscription_templates/{}/checkout_identifier* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Moneybird API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Moneybird API 4
-
POST /api/v2/{}/webhooks*Endpoint removal Stopped working -
No date
DELETE /api/v2/{}/purchase_transactions/{}/delete*Endpoint removal Deprecated, no date -
No date
GET /api/v2/{}/import_mappings/*Endpoint removal Deprecated, no date -
No date
GET /api/v2/{}/reports/ledger_accounts/{}*Endpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.