How to get access to make SOAP API Calls to an ACC v7instance | Community
Skip to main content
I
ibalbale
Level 2
March 10, 2026
Solved

How to get access to make SOAP API Calls to an ACC v7instance

  • March 10, 2026
  • 1 reply
  • 31 views

I am looking to make API calls to ACC v7 using SOAP. What permissions should the user have and where do you set these permissions.

Should the instance be configured to allow SOAP Logon with an Adobe ID, or do I need a separate Technical Operator account for API calls?

Best answer by Nolan_Chabert

Hi @ibalbale,

The instance configuration will depend on the type of authentication you are using (username/password or token-based connection).

User permissions should be defined based on the activities you plan to perform on the instance. One approach is to grant administrative rights while disabling UI access. This allows full platform capabilities (depending on your SOAP requests) without granting interactive access. Alternatively, you can apply more granular permissions by restricting access to specific folders and workflows required for execution.

For efficiency during testing, I recommend initially granting broader permissions and then progressively restricting them until you reach the appropriate level of access for your use case.

Thanks.

Regards,
Nolan

Nolan 

1 reply

Nolan_Chabert
Adobe Employee
Nolan_ChabertAdobe EmployeeAccepted solution
Adobe Employee
March 11, 2026

Hi @ibalbale,

The instance configuration will depend on the type of authentication you are using (username/password or token-based connection).

User permissions should be defined based on the activities you plan to perform on the instance. One approach is to grant administrative rights while disabling UI access. This allows full platform capabilities (depending on your SOAP requests) without granting interactive access. Alternatively, you can apply more granular permissions by restricting access to specific folders and workflows required for execution.

For efficiency during testing, I recommend initially granting broader permissions and then progressively restricting them until you reach the appropriate level of access for your use case.

Thanks.

Regards,
Nolan

Nolan 

    I
    ibalbaleAuthor
    Level 2
    March 11, 2026

    I am using token based authentication. 

    The Product Profiles added for the Technical User are

    Campaign -

    https://<sandbox_instance>/view/home - workflowSupervisor https://<sandbox_instance>/view/home - workflow,
    https://<sandbox_instance>/view/home - delivery,
    https://<sandbox_instance>/view/home - admin


    Are these sufficient to query all schemas, get schema details including all attributes, get all recipients etc. mostly a full access in the beginning?

    I am already having difficulty getting schema details. Schema list works fine. recipients with limited attributes works, request with wider attributes throw SOP-330011 errors.

     

    Nolan_Chabert
    Adobe Employee
    Nolan_ChabertAdobe Employee
    Adobe Employee
    March 11, 2026

    Hi @ibalbale,

    Since the login using the admin operator has been successfully validated, the initial access question is now resolved.

    At this point, the issue appears to be related to the API call itself. This would move us into API-level debugging, which is a separate topic from the authentication/permission question. It may be best to open a new ticket specifically focused on the API behavior so we can properly investigate the request structure, method used (OOTB vs custom), and any JavaScript logic behind it.

    Please let me know if you can share the API call details in a new thread, and we can continue the troubleshooting from there.

    Thanks.

    Regards,
    Nolan

    Regards,
    Nolan

    Terms & ConditionsAccessibility statement

    Loading footer...