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.
Log in to comment and vote
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.