Running into a Confusing 403 Error

Austen Brown · August 20

{

  "error": {

    "code": 403,

    "source": "flow-apim-msmanaged-na-eastus2-01.azure-apim.net",

    "clientRequestId": "7567d9d5-55ba-40aa-a4f2-18a346eafa38",

    "message": "The response is not in a JSON format.",

    "innerError": "Cannot read server response."

  }

Building a flow that utilizes tribute information. Getting the above error for a "List gift tributes" action. I've confirmed that I have access to tribute records in both DBV and WV. This action works in other environments/databases; at a loss as to what this means and how to fix it. Any insight would be appreciated.

Alex Wong · August 21

Can you provide more info on the request header/parameters/body and response (from a run history) of everything it responded back?

Carol Grant · August 21

I'm sure you know this already but this is the one that you need to manually put in the Gift ID. I'm going to assume you are looping around List Gifts or from Get a Gift. So you need to have an expression in the List Gift Tributes that pulls in the Gift ID. Something like this: items('Apply_to_each')?['id']

It can't be dynamic content.

Austen Brown · August 21

This action is in a child flow, so it's not in a loop - only one gift runs through the flow at time.

Edit Mode

Result Screeshoot

Result Entire Output

Alex Wong · August 21

Forbidden: the issue may be related to gift tributes requires additional access right as it is in the NXT Data Integration section of the SKY API, which used to required solution admin to run.

Please note: This API currently requires that the consenting user has the Extensibility role with NXT Data Integration API task permission.

I assume you are doing this for a client of yours, you might want to check the permission given.

Alex Wong · August 21

check the user you are using to run SKY API for one of the red circled rights

Austen Brown · August 21

Thank you! I'll check in with them on this!

Austen Brown · August 22

@Alex Wong that did it! Thank you!!!

Running into a Confusing 403 Error

Answers

Categories