Passing a Bearer authorization token as a custom HTTP header (rather than through a Routing Address's built-in Authentication Method) when calling an outbound REST endpoint from PL/SQL results in a 401 Unauthorized, even though the header appears to be built correctly.

Q: Passing a Bearer authorization token as a custom HTTP header (rather than through a Routing Address's built-in Authentication Method) when calling an outbound REST endpoint from PL/SQL results in a 401 Unauthorized, even though the header appears to be built correctly.

Passing a custom Authorization: Bearer ... header through the REST-sender API's own request-headers parameter is a valid, working pattern (rather than relying on the Routing Address's built-in authentication method) — if it still comes back 401, check whether the token itself has simply expired before assuming the header-passing mechanism is broken, since an expired token produces exactly this symptom despite the request otherwise being constructed correctly.

Answer

Passing a custom Authorization: Bearer ... header through the REST-sender API's own request-headers parameter is a valid, working pattern (rather than relying on the Routing Address's built-in authentication method) — if it still comes back 401, check whether the token itself has simply expired before assuming the header-passing mechanism is broken, since an expired token produces exactly this symptom despite the request otherwise being constructed correctly.

← Browse Integrations and APIs questions