Response 502 while using production instance





We have two different projects with in, each with a connection to the Adobe campaign API, which in turn have different product profiles. One project and instance is for staging, and one for production. We are successfully using the staging instance via REST API, for creating user profiles and triggering events, but when using the production instance in the same manner we are running into problems. There are no apparent differences in configuration between the two instances that can explain this issue, and we need help finding debug information.


When we try to make a call to the production API using production token and keys we get the following:



curl --request GET \
--url{OUR TENANT ID}/campaign/profileAndServices/resourceType/profile \
--header 'authorization: Bearer [our valid access token here]' \
--header 'cache-control: no-cache' \
--header 'content-type: application/json' \
--header 'x-api-key: [our API key here]'


"code": 502,
"message": "Oops. Something went wrong. Check your URI and try again."


The header includes the following (Note the double // which we do not get in the staging instance case):

X-Debug-Backend: https://{OUR TENANT ID}


Both instances are running: Adobe Campaign v20.3 build 10586


Is it possible to get access to debug logs or anything similar in order to understand the cause of the 502? Neither ourselves or our Implementation Partner have been able to identify any configuration difference between our production and staging instances, so we are running out of ideas.


Thanks for any advice on how to trouble shoot or fix this issue!


Adobe Campaign Standard rest api

Accepted Solutions (1)

Accepted Solutions (1)



Solution comment by Adobe: "Such kind of issues comes when integration is not done correctly. So the reason why the API integration is not working for you might be using the integration created for Stage instance for firing API calls on Prod.


If there is single integration point created which is linked to Stage instance and if someone will use it for firing calls to Production instance it will not work. You have to create two separate integrations for stage and prod and accordingly use the same.


The reason we need individual integration is because at the time of creating in Adobe I/O it we define the product configuration to use and for one integration you can link a product configuration either for prod or for stage."


Unclear what "integration was not not done correct", but its working now...

Answers (0)