Adobe Target Profile bulk update endpoint returns inconsistent result

[wangheok]

Hi all,

We have configured a new Target integration recently and testing with profile bulk update api but the result returned by adobe side were inconsistent. However, it returned the response below even the previous runs were okay. The access token is valid for 90 days so I'm not sure who the reason would make the token not recognized...

curl -X POST  --data-binary @Deleted Account.csv http://n3hubapacpartnersand.tt.omtrdc.net/m2/n3hubapacpartnersand/v2/profile/batchUpdate -H "Authorization: Bearer 9f777f52-2632-4b3c-b3d8-9a1bd6dad1ca" -i


HTTP/1.1 403 
Date: Tue, 22 Mar 2022 02:22:08 GMT
Content-Type: application/xml
Transfer-Encoding: chunked
Connection: keep-alive
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: 0
X-Frame-Options: DENY

<string>Authentication failed, make sure a valid token is provided</string>%   

Cheers

Frank

[Kishore_Reddy · Accepted solution]

Very interesting! Have you tried replicating this multiple times and with other users' access. 

Also, consider the caveats mentioned here: https://experienceleague.adobe.com/docs/target/using/implement-target/before-implement/methods/bulk-...