Migration from "Get Campaigns" Endpoint in Legacy API to New Revision: Clarification Needed

Question

While transitioning from the Legacy API to the new revision, I encountered the following under the 'relationships' section in the sample response of the new API:

"relationships": { "campaign-messages": { "data": [ { "type": "campaign-message", "id": "string" } ], }

I noticed that the data for "campaign-messages" is presented in an array format, implying that there could be multiple campaign messages associated with a single campaign.

Could someone please confirm if my understanding is correct? If it is, could I also get an explanation or a potential scenario in which a campaign would incorporate more than one campaign message? Any insights would be appreciated.

Kim Strauch · Accepted Answer

Hey @santiagosanti! A campaign will typicallyhave one message associated with it but could have multiple messages in the case that an A/B test has been configured. In that case I believe you may have a campaign message for each of the variations in your test.

santiagosanti · Answer

Hello,I have some concerns and questions regarding the migration from the Legacy API to the new revision API to get campaign related data. I have not yet migrated to the new revision API because I have observed that it may not offer the same level of performance as the legacy API.In the legacy API, all the necessary data, includedandexcluded list attributes, campaign message attributes, and total recipients, is available in a single API call. However, in the new revision API, it seems that I would need to make multiple API calls to retrieve the same information. This could potentially slow down the data retrieval process and impact performance.Additionally, I am having difficulty locating where I can retrieve the "campaign - is segmented" value by campaign ID in the new API.Thank you for your assistance. I look forward to your response.

Sign up

Use your Klaviyo credentials

Log in to the Community

Use your Klaviyo credentials