Legacy Dev Forum Posts

 View Only

Sign Up

Unexpected 403 Error when Role has permissions

  • 1.  Unexpected 403 Error when Role has permissions

    Posted 06-05-2025 18:17

    Lloyd | 2020-08-12 21:16:22 UTC | #1

    We have a scenario where a customer has brought another customer, both of whom are running PureCloud. My brief is to migrate them into a single Org.

    I've created an client credentials OAuth account in both orgs, with roles correctly assigned for the permissions required.

    When I try run POST /api/v2/architect/prompts I get a 403 response. The API Explorer says the permission required is architect:userPrompt:add which I have confirmed the role used by the OAuth has.

    Same issue occurs for POST /api/v2/routing/queues

    My guess is that this must be done under an implicit grant rather than client credentials, but thought I would double check this as it doesn't appear to be documented as such.

    Thanks


    tim.smith | 2020-08-18 14:44:36 UTC | #2

    A 403 response means you are lacking access in some capacity. The error message in the response should indicate what the issue is. Can you share the errors you're getting?


    Lloyd | 2020-08-21 03:22:38 UTC | #3

    Tim,

    I worked it out finally, and really obvious afterwards.

    The Resource was in a Division that the Role assigned to me OAuth did not have.

    Sorry to trouble you

    Thanks Lloyd


    system | 2020-09-21 03:22:42 UTC | #4

    This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.


    This post was migrated from the old Developer Forum.

    ref: 8563