sessionID parameter for the Target REST API | Community
Skip to main content
R
RJBu
May 23, 2022
Solved

sessionID parameter for the Target REST API

  • May 23, 2022
  • 2 replies
  • 1619 views

Is it an acceptable pattern to use the mbox cookie session value as sessionID parameter for the Target REST API calls?

 

https://developers.adobetarget.com/api/delivery-api/

 

 

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Rajneesh_Gautam_

    hi @rjbu  - Adobe Target Session-id must follow following rules which are explained here: https://experienceleague.adobe.com/docs/core-services/interface/administration/ec-cookies/cookies-target.html?lang=en#

     

    • The Session ID can be any printable string except a space, question mark ( ? ), or a forward slash ( / ).
    • The Session ID should be from 1 through 128 characters in length.

    Hope this helps,

     

    Regards

    Rajneesh

    2 replies

    Rajneesh_Gautam_
    Community Advisor
    Rajneesh_Gautam_Community AdvisorAccepted solution
    Community Advisor
    May 29, 2022

    hi @rjbu  - Adobe Target Session-id must follow following rules which are explained here: https://experienceleague.adobe.com/docs/core-services/interface/administration/ec-cookies/cookies-target.html?lang=en#

     

    • The Session ID can be any printable string except a space, question mark ( ? ), or a forward slash ( / ).
    • The Session ID should be from 1 through 128 characters in length.

    Hope this helps,

     

    Regards

    Rajneesh

      Tanvi_Agarwal_
      Adobe Employee
      Tanvi_Agarwal_Adobe Employee
      Adobe Employee
      May 31, 2022

      Hi @rjbu 

       

      Yes, you can use the same mbox cookie session value in Delivery API. However it can affect the current user session if its still LIVE, incase you are updating the parameters.

       

      So if the format is in question, then you can use it. But using the same session ID or different should depend on the usecase for which APIs are used.

        Terms & ConditionsAccessibility statement

        Loading footer...