Hi everyone! We're very excited to announce some great progress on a REST API for our web application. We've just released a preview of the structure for our new "Campaigns API" here: https://developers.getvero.com
Whilst not yet publicly available (there isn't an authentication mechanism) we would love your feedback on how we're approaching the API. To date we've published three endpoints for the most fundamental features: campaigns but we're working on more for segments, etc.
If you have any feedback please leave it here or email us on support@getvero.com. We want to know what you'd use the API for and if there's anything that would mean the current design direction doesn't meet your needs!
Silver Milkshake
•
Aug 10, 2023
Chris Hexton: Great news mate! Keeping a close eye on this one! :)
Blush Cascade
•
Apr 3, 2025
Hi - After 1 year, is this API ready for release now? We’d love access to this.
Tomato Beach
•
Dec 8, 2020
I'd be perfectly happy if we could get access to just the templates and raw html of the email.
Black Teacup
•
Jan 16, 2020
The API needs read/write access
Chris Hexton
Team•
Jul 8, 2024
As we continue to work on Multi-message campaigns (Workflows) in Vero 2.0 we are making further changes to our API structure. Once we have released this feature we believe we will be in a position to release this fully :).
Blush Cascade
•
Apr 3, 2025
Hi - After 1 year, is this API ready for release now? We’d love access to this.
Chris Hexton
Team•
Apr 4, 2025
Hi there, we’re due to add some updates to the API documentation soon regarding A/B tests (
Once we finalise this feature in the API we will then be in a position to release the API. Until that point the Campaigns object may undergo further significant change and we do not want to release it publicly until it’s released stability.
This release set us up to generate API keys that work with the new Campaigns API:
Happy to answer further Qs. We are working to get this live as soon as we can. Curious: what is your use case for this? I.e. backing up campaigns? Something else?
Rose Crater
•
Apr 7, 2025
Hi - Thanks for the reply. Our use case for the campaign API is to setup campaigns programmatically so that less human involvement is required from an operation standpoint. We have 20+ languages and everytime the human effort involved is ridiculous.
Chris Hexton
Team•
Apr 7, 2025
Yes, we are aware that managing 5+ languages becomes challenging with Vero. We are excited for the API for this reason.
We are doing all we can internally to get this live and will let you know as soon as it is.
In the interim, have you considered the “Data Feeds”/Fusion feature to handle this?
As we cache API responses this can work well. Several customers have used this approach to scale to 20+ languages. It’s a “pull”-based approach rather than you pushing the languages to us via API but could be a stop-gap. Happy to discuss if you’d like with our success team.
Blush Cascade
•
Apr 3, 2025
Is the Campaign API ready for release now? We’d very much like access to this API. Thanks.
We’ll have more releases coming regarding the API and MCP server in the coming couple of weeks (this release is the first of several rolling releases towards our MCP server). Please ask us any Qs!
Log in to comment and vote
Comments14
Apr 23
PinnedHi all, we’ve released our first public API endpoints for managing campaign content:
https://help.getvero.com/api-reference/campaigns/get-a-campaign
If you’d like access, please let us know!
Chris Hexton
Aug 10, 2023
Hi everyone! We're very excited to announce some great progress on a REST API for our web application. We've just released a preview of the structure for our new "Campaigns API" here: https://developers.getvero.com
Whilst not yet publicly available (there isn't an authentication mechanism) we would love your feedback on how we're approaching the API. To date we've published three endpoints for the most fundamental features: campaigns but we're working on more for segments, etc.
If you have any feedback please leave it here or email us on support@getvero.com. We want to know what you'd use the API for and if there's anything that would mean the current design direction doesn't meet your needs!
Silver Milkshake
Aug 10, 2023
Chris Hexton: Great news mate! Keeping a close eye on this one! :)
Blush Cascade
Apr 3, 2025
Hi - After 1 year, is this API ready for release now? We’d love access to this.
Tomato Beach
Dec 8, 2020
I'd be perfectly happy if we could get access to just the templates and raw html of the email.
Black Teacup
Jan 16, 2020
The API needs read/write access
Chris Hexton
Jul 8, 2024
As we continue to work on Multi-message campaigns (Workflows) in Vero 2.0 we are making further changes to our API structure. Once we have released this feature we believe we will be in a position to release this fully :).
Blush Cascade
Apr 3, 2025
Hi - After 1 year, is this API ready for release now? We’d love access to this.
Chris Hexton
Apr 4, 2025
Hi there, we’re due to add some updates to the API documentation soon regarding A/B tests (
https://developers.getvero.com/application-api-reference/) and a few other improvements.
We are currently working on adding Workflows/Automations to Vero 2.0:
https://feedback.getvero.com/p/multi-message-campaigns-workflows-in-connect
Once we finalise this feature in the API we will then be in a position to release the API. Until that point the
Campaignsobject may undergo further significant change and we do not want to release it publicly until it’s released stability.This release set us up to generate API keys that work with the new Campaigns API:
https://feedback.getvero.com/changelog/tracking-api-key-management-in-vero-20
Happy to answer further Qs. We are working to get this live as soon as we can. Curious: what is your use case for this? I.e. backing up campaigns? Something else?
Rose Crater
Apr 7, 2025
Hi - Thanks for the reply. Our use case for the campaign API is to setup campaigns programmatically so that less human involvement is required from an operation standpoint. We have 20+ languages and everytime the human effort involved is ridiculous.
Chris Hexton
Apr 7, 2025
Yes, we are aware that managing 5+ languages becomes challenging with Vero. We are excited for the API for this reason.
We are doing all we can internally to get this live and will let you know as soon as it is.
In the interim, have you considered the “Data Feeds”/Fusion feature to handle this?
https://help.getvero.com/vero-1/articles/localization-strategies/#using-json
As we cache API responses this can work well. Several customers have used this approach to scale to 20+ languages. It’s a “pull”-based approach rather than you pushing the languages to us via API but could be a stop-gap. Happy to discuss if you’d like with our success team.
Blush Cascade
Apr 3, 2025
Is the Campaign API ready for release now? We’d very much like access to this API. Thanks.
Chris Hexton
Apr 4, 2025
Please see my response here:
https://feedback.getvero.com/p/api-access-to-all-features-in-the-ui-such-as/comment/67f001436274f30615077553
Chris Hexton
Jul 8
Hi all, we’ve released new endpoints today. These endpoints allow you to:
List all broadcasts and journeys.
Read all broadcasts, A/B test contents and localised versions of the content.
Read all journeys, including the full graph of nodes and “edges” (i.e. the journey itself).
Read all journey messages, including all localised versions of the content.
Create and update broadcasts (you can’t include an audience at this time, but that’s coming shortly!)
You can read the updated documentation here:
https://help.getvero.com/api-reference/overview
We’ll have more releases coming regarding the API and MCP server in the coming couple of weeks (this release is the first of several rolling releases towards our MCP server). Please ask us any Qs!