Moneybird API
DELETE /api/v2/{id}/purchase_transactions/{id}/delete* endpoint removal
Deprecated, no dateSubscribe to Moneybird APIShare
Moneybird has deprecated the DELETE /api/v2/{id}/purchase_transactions/{id}/delete* endpoint without a shutdown date. Calls made to this route are slated for removal and will eventually fail. Moneybird API noted that the endpoint deprecated notice was announced on August 18, 2025.
Calls it hits
DELETE /api/v2/{id}/purchase_transactions/{id}/delete*
What to use instead of these calls
Delete with DELETE /api/v2/{administration_id}/purchase_transactions/{id} instead.
In Moneybird API's words
DELETE /{administration_id}/purchase_transactions/{id}/delete{format} - endpoint deprecated
Facts
- API
- Moneybird API
moneybird.com - Kind
- Endpoint removal
- Announced
- August 18, 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 DELETE /api/v2/{id}/purchase_transactions/{id}/delete* 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/{id}/webhooks*Parameter removal Stopped working -
No date
GET /api/v2/{id}/import_mappings/*Endpoint removal Deprecated, no date -
No date
GET /api/v2/{id}/reports/ledger_accounts/{id}*Endpoint removal Deprecated, no date -
No date
GET /api/v2/{id}/subscription_templates/{id}/checkout_identifier*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.