Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

srjoshi
Community profile srjoshi Level 2
Job title here
Location here
7 BADGES
Level 2

Level 2

Learn more
Joined the community 27-07-2020 4:11:23 PM
Offline
Top badges earned by srjoshi
Customize the badges you want to showcase on your profile
Re: External API - WKF-560237 Activity failed (reason: 'H...
Avatar
Give Back 5
Level 2
srjoshi
Level 2

Likes

4 likes

Total Posts

5 posts

Correct reply

4 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 3
Boost 1
View profile
srjoshi
- Adobe Campaign Standard
The activity seems to have failed due to a HTTP 400 error from the third-party API. If you are getting the same error from the third-party API when using Postman, then the issue is most likely due to how you are calling the API.

Views

255

Likes

2

Replies

0
Re: External API work flow
Avatar
Give Back 5
Level 2
srjoshi
Level 2

Likes

4 likes

Total Posts

5 posts

Correct reply

4 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 3
Boost 1
View profile
srjoshi
- Adobe Campaign Standard
As long as it would be feasible to serialize the unverified user contacts into a JSON within the payload size limits (5MB), it might work. However, there are other details from this question that are not mentioned here, that will also determine the feasibility of creating such a workflow. Specifically, it is not clear whether the push notification will need to be sent to each user in unverified segment, whether the push tokens exist in ACS etc. From External API point of view, the main points to...

Views

324

Like

1

Replies

0
Re: External API - Custom Payload body
Avatar
Give Back 5
Level 2
srjoshi
Level 2

Likes

4 likes

Total Posts

5 posts

Correct reply

4 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 3
Boost 1
View profile
srjoshi
- Adobe Campaign Standard
External API activity will show the format of the request body JSON format that will be generated on the Inbound Mapping tab of the activity, under Post Body Template. This format is also shown in the documentation - https://docs.adobe.com/content/help/en/campaign-standard/using/managing-processes-and-data/data-management-activities/external-api.html#description The request body format is not customizable at this time. Hope this helps.

Views

513

Like

1

Replies

0
Re: Dynamic OAuth verification in External API activity
Avatar
Give Back 5
Level 2
srjoshi
Level 2

Likes

4 likes

Total Posts

5 posts

Correct reply

4 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 3
Boost 1
View profile
srjoshi
- Adobe Campaign Standard
Until External API activity adds built-in support for OAuth token retrieval, the marketer (or consultant helping the customer) will need to refresh the OAuth token every 24 hours (or other expiry times) and configure those in the workflow activity Execution tab where one can specify any custom Headers to be sent on the API call.

Views

360

Likes

0

Replies

0
Re: ACS External API
Avatar
Give Back 5
Level 2
srjoshi
Level 2

Likes

4 likes

Total Posts

5 posts

Correct reply

4 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back
Boost 3
Boost 1
View profile
srjoshi
- Adobe Campaign Standard
Workflow execution logs will typically show you the various steps taken during the execution of that workflow, including the URLs of external API endpoints to which calls are made. Whether GET or POST method is used during the call is based on whether there is any request body to be sent to the API endpoint or not. If the problem is not yet resolved, you can submit the log messages from the workflow to this post for further troubleshooting help.

Views

439

Likes

0

Replies

0
Likes from