Expand my Community achievements bar.

Join us on September 25th for a must-attend webinar featuring Adobe Experience Maker winner Anish Raul. Discover how leading enterprises are adopting AI into their workflows securely, responsibly, and at scale.
SOLVED

On Demand Segment Evaluation

Avatar

Level 4

Dear community,

 

I've been trying to create an On Deman Segment Evaluation but I keep getting the same error (Attached in images). The link I followed is here (https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-19251) I tried using all types of Audiences (Published, Draft, using already created, and newly created audience). I have attached the body below and the URL Endpoint is (https://platform.adobe.io/data/core/ups/segment/jobs). Please guide me onto how I could resolve this issue and do not hesitate if you need any more information.

 

JSON Body Below : 

{
   "segmentId": "de252a01-c4f8-473b-99ec-341db56221ca"
}



Best regards

Sching

1 Accepted Solution

Avatar

Correct answer by
Level 5

It is supposed to be an array of JSON body : 

View solution in original post

4 Replies

Avatar

Community Advisor

Hello @ChanuteJo 

I have never encountered this error when attempting to create an on-demand job. Can you validate that the segment ID you are using is not missing a character?

Avatar

Correct answer by
Level 5

It is supposed to be an array of JSON body : 

Avatar

Employee

Hello @ChanuteJo 

 

It appears your syntax in your body is not correct. 

 

Please update your body to include the array notation as noted below.  This will execute a single segment.

[
{
   "segmentId": "de252a01-c4f8-473b-99ec-341db56221ca"
}
]

 

you can use the following for multiple segments in a single call.

 

[{
   "segmentId": "de252a01-c4f8-473b-99ec-341db56221ca"
},
{
   "segmentId": "segment2"
},
{
   "segmentId": "segment3"
}


]

Avatar

Level 5

Yes as others have stated it needs the brackets, even for a singular one. 

[
    {
    "segmentId": "segmentIDHERE"
    }
]

I totally understand your confusion though, the documentation you sited was incorrect!