ACC Campaign Call from postman/external tool | Community
Skip to main content
Level 2
May 9, 2026
Solved

ACC Campaign Call from postman/external tool

  • May 9, 2026
  • 4 replies
  • 179 views

Hi ,

My requirement is to access Adobe Campaign Classic campaign details based on Campaign ID or PK from an external tool. As an initial step, I am trying to test the integration using Postman or SOAP UI.

For this setup, I need to create an operator/user with API access but without access to the ACC client console (forbidden console access). However, user and access management in our environment is currently handled only through Adobe Admin Console.

Could you please help me understand:

  • How can I create such an API-only operator through Admin Console?
  • What would be the recommended process for this setup?
  • Is there any alternative approach or workaround for enabling external API access in this scenario?

Thank you for your support.

Best regards,
Ankita Vishe

    Best answer by Amine_Abedour

    Hello ​@AnkitaVi1,

     

    Please find bellow documentation on how to create a technical operator consume Adobe campaign APIs:
    https://experienceleague.adobe.com/en/docs/campaign/technotes-ac/tn-new/ims-migration

    After first call to any API using this operator, an operator will be created in adobe campaign classic, you can then forbid access from the rich client to this technical operator.
    Br,

    4 replies

    Amine_Abedour
    Community Advisor
    Amine_AbedourCommunity AdvisorAccepted solution
    Community Advisor
    May 9, 2026

    Hello ​@AnkitaVi1,

     

    Please find bellow documentation on how to create a technical operator consume Adobe campaign APIs:
    https://experienceleague.adobe.com/en/docs/campaign/technotes-ac/tn-new/ims-migration

    After first call to any API using this operator, an operator will be created in adobe campaign classic, you can then forbid access from the rich client to this technical operator.
    Br,

    Amine ABEDOUR
    AnkitaVi1Author
    Level 2
    May 14, 2026

    Thanks for the reply!

    Using the documentation, I was able to generate the session token successfully. Now I’m trying to retrieve campaign details for a specific campaign through the queryDef method. However, I’m facing an error with this approach. Interestingly, when I used the workflow start method, it worked fine — but the queryDef request is not returning the expected result.

     


     

     

    Ankita Vishe
    Amine_Abedour
    Community Advisor
    Community Advisor
    May 14, 2026

    Hello ​@AnkitaVi1,

    Please try using these two headers :
     

    Your query definition isn't right either; it should look like 

    <queryDef operation="select" schema="nms:operation">
    <select>
    <node expr="@id"/>
    <node expr="@internalName"/>
    <node expr="@label"/>
    <node expr="@status"/>
    <node expr="@start"/>
    <node expr="@end"/>
    </select>
    <where>
    <condition expr="@id = 16000"/>
    </where>
    </queryDef>

     

    Amine ABEDOUR
    AnkitaVi1Author
    Level 2
    May 18, 2026

    Thank You so much. This was fixed and it worked

    Ankita Vishe