topic Utility - HTTP - 10.0.0: HTTP Request File in Digital Exchange

Utility - HTTP - 10.0.0: HTTP Request File

rachkim1617 — Fri, 30 Dec 2022 15:56:26 GMT

I am using an Ariba API to download a file and received a response, but need to use the HTTP Request File action to save a PDF file. I filled out the Address URL, Method, Accept, Use Bearer Token, Bearer Token, and File Path inputs and stepped through the action, but received a 401 status code: remote server returned an error: (401) Unauthorized.

How do I format the headers collection to use the Request File action? Is there anything else needed?

Re: Utility - HTTP - 10.0.0: HTTP Request File

ewilson — Mon, 02 Jan 2023 15:55:47 GMT

@rachkim1617,

There are multiple Ariba APIs. Can you be more specific about which one you're using?

Cheers,
Eric

Re: Utility - HTTP - 10.0.0: HTTP Request File

ewilson — Mon, 02 Jan 2023 16:07:08 GMT

FWIW - Here's a screenshot of the SAP Ariba connector on the DX and the common headers it sets. Note: The Authorization header is automatically created and populated by your use the Bearer Token parameter on the HTTP VBO.

Cheers,
Eric

Re: Utility - HTTP - 10.0.0: HTTP Request File

rachkim1617 — Tue, 03 Jan 2023 15:09:37 GMT

@ewilson Thank you for the quick response! I'm using the Project Document Management Download API (Project Document Management API endpoints | SAP Help Portal). I copied the common headers from BluePrism SAP Ariba connector for this API and created a single row Headers collection to use in the HTTP Request File action (Fields: Content-Type, APIKey, accept, Authorization)

But I am getting the following error message after running this action:

ERROR: internal: Could not execute code stage because exception thrown by code stage: The 'Content-Type' header must be modified using the appropriate property or method.

I set current values for Content-Type as application/json and accept: application/pdf

Re: Utility - HTTP - 10.0.0: HTTP Request File

ewilson — Tue, 03 Jan 2023 16:06:22 GMT

@rachkim1617,

There's a dedicated Content-Type property exposed by the actions on the HTTP VBO, so you don't need to add that to the Headers Collection.

Cheers,
Eric