![]()
api.brevo.com · MarketingSubscribeShare
Brevo breaking changes
The breaking changes Brevo announced that Okapi tracks: 3 in all.
Do you run the Brevo API? Make sure your users call it right →
At a glance
- API host
api.brevo.com- Kind
- Marketing
- Versions with breaking changes
- v3 (3)
- Breaking changes tracked
- 2 breaking changes with no date yet and 1 already in effect
- Last updated
Deprecated, no date yet 2
-
No date
/v3/reseller/*Endpoint removal Deprecated, no date -
No date
POST /v3/transactionalSMS/smsEndpoint removal Deprecated, no date
Already in effect 1
-
POST /v3/contacts/batchEndpoint removal Stopped working
Where Okapi reads it
- Changelog developers.brevo.com/changelog
- OpenAPI spec developers.brevo.com/openapi/contact-management.json
- OpenAPI spec developers.brevo.com/openapi/email-api.json
- Announcement developers.brevo.com/changelog/2024/7/9
- Announcement developers.brevo.com/changelog/2025/5/1
- Announcement developers.brevo.com/changelog/2026/5/12
Know before your API calls break.
Okapi finds the calls a breaking change hits in your code and opens the pull request that fixes them.
Add to GitHub