Skip to main content
Contributor IV
June 21, 2023
Solved

Is Oauth needed for API v3 usage?

  • June 21, 2023
  • 2 replies
  • 257 views

We have an integration that uses the older API’s.  For example I just make a cURL request to

https://a.klaviyo.com/api/v1/lists?api_key=xyz

Will I still be able to do this by passing the api_key with v3 endpoints or do I need to authenticate first with oauth now?  

And if so can I just convert to the lack of a v# like the docs say is not used anymore?  
For example: https://a.klaviyo.com/api/lists?api_key=xyz ?  is that all that is needed?

 

 

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

    Hi @kenw232!

    My apologies for the delay here - oAuth is not required to make a V3 API call. To answer your second question - yes, as long as you include your api key in the header, the new V3 APIs do not require the ‘V3’ identifier. It’s also recommended to use our dynamic documentation to build your request so that it’s formatted correctly.

     

    Thanks for using the Community!

    - Brian

    2 replies

    Brian Turcotte
    Klaviyo Alum
    June 22, 2023

    Hi @kenw232!

    I’m going to check with Engineering on this and I’ll update the thread as soon as possible!
     

    - Brian

    Brian Turcotte
    Klaviyo Alum
    June 28, 2023

    Hi @kenw232!

    My apologies for the delay here - oAuth is not required to make a V3 API call. To answer your second question - yes, as long as you include your api key in the header, the new V3 APIs do not require the ‘V3’ identifier. It’s also recommended to use our dynamic documentation to build your request so that it’s formatted correctly.

     

    Thanks for using the Community!

    - Brian