How aem-target integration works behind | Community
Skip to main content
July 15, 2020
Solved

How aem-target integration works behind

  • July 15, 2020
  • 2 replies
  • 1185 views

Guys,

 

I was trying to understand how aem xf "export to target" works.

 

As per analysis aem is sending a post call to target api with all the details like clientcode, mail, password, operations and content.


And as a return it responds with offerid.


And this offerid would be used for update and delete the xf in target.


These i understood via codebase. But when i try to do the same in postman I am getting issue .

I got a issue like 403 legacy api access denied. Do I need to add at.js somewhere in postman to avoid the issue? Or May I know how to try via postman?

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 aemmarc2

Re : 403 legacy api access denied.

 

This is coming from Target. Probably better suited to field that question with them than AEM.

 

Just going a quick skim it looks like in Nov 2017 these Target Classic legacy api's were blocked as part of TNT-27260

 

 

2 replies

aemmarc2Adobe EmployeeAccepted solution
Adobe Employee
July 16, 2020

Re : 403 legacy api access denied.

 

This is coming from Target. Probably better suited to field that question with them than AEM.

 

Just going a quick skim it looks like in Nov 2017 these Target Classic legacy api's were blocked as part of TNT-27260

 

 

Shashi_Mulugu
Community Advisor
Community Advisor
July 18, 2020