Brevo
POST /v3/transactionalSMS/sms endpoint removal
Deprecated, no dateSubscribe to BrevoShare
Brevo announced on May 1, 2025, that POST /v3/transactionalSMS/sms has been deprecated without a shutdown date. Brevo retired this former endpoint in favor of a more stable and simplified version. Once removed, requests sent to this endpoint fail.
Calls it hits
POST /v3/transactionalSMS/sms
What to use instead of these calls
Use POST /v3/transactionalSMS/send instead.
In Brevo's words
We’ve deprecated the former transactional SMS endpoint in favor of a more stable and simplified version.
Facts
- API
- Brevo
api.brevo.com - Kind
- Endpoint removal
- Announced
- May 1, 2025
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Brevo's own pages
Questions
When does this change take effect?
Brevo deprecated POST /v3/transactionalSMS/sms without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Brevo 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 Brevo 2
-
POST /v3/contacts/batchEndpoint removal Stopped working -
No date
/v3/reseller/*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.