Skip to main content
Problem Solver I
December 6, 2022
Solved

Brick & Mortar Integration with NEW APIs

  • December 6, 2022
  • 2 replies
  • 204 views

We are starting a project to integrate our bricks-and-mortar transaction data into Klaviyo.  The article on the developers site has been a great starting point: Sync Ecommerce with Brick-and-Mortar Locations | Klaviyo Developers 

I am wondering if there is a similar resource for the new API (22-10-17) endpoints?    The v1/v2 docs are pointing towards posting data via the server-side ‘track’ api, but now it appears I should be using the ‘events’ endpoint.  

Should I continue with v1/v2 for now, with the intent to upgrade to the new calls before the end of 2023?  

Any guidance would be appreciated.   Thanks!

This topic has been closed for replies.
Best answer by Brian Turcotte

Hi @ksp_john and welcome back to the Community!

 

While the Brick-and-Mortar guide is still mostly relevant, the code snippets listed there still use the legacy APIs. I spoke with our engineering/technical writing team about the guides, and they informed me that they will be updated in the next month or so to reflect the latest APIs. 

 

To that end, I would suggest continuing with the legacy APIs, and I will update the thread when the new documentation is available!

 

I hope this helps to clarify!

 

Thanks, 

Brian

2 replies

Brian Turcotte
Klaviyo Alum
December 7, 2022

Hi @ksp_john and welcome back to the Community!

 

While the Brick-and-Mortar guide is still mostly relevant, the code snippets listed there still use the legacy APIs. I spoke with our engineering/technical writing team about the guides, and they informed me that they will be updated in the next month or so to reflect the latest APIs. 

 

To that end, I would suggest continuing with the legacy APIs, and I will update the thread when the new documentation is available!

 

I hope this helps to clarify!

 

Thanks, 

Brian

ksp_johnAuthor
Problem Solver I
December 8, 2022

@Brian Turcotte - Thank you for the feedback and guidance.  We will move forward with the legacy APIs for now -- but certainly looking forward to the new documentation!