MuleSoft · HTTP Connector
No access token found
Short answer
No access token found means an HTTP request with OAuth 2.0 authentication ran before any access token had been obtained. Call the authorization URL at least once first, or store the token and refresh it.
VerifiedLast verified
01Error text
No access token found. Verify that you have authenticated before trying to execute an operation to the API02Likely causes
- The operation ran before the OAuth 2.0 authorization had been completed, so there is no access token to send.
03How to fix it
- Call the authorization URL at least once so that an access token is obtained.
- Or store the token in an Object Store and refresh it.
- Run the operation again after the token exists.
iNotes
For DocuSign, the docs suggest using DocuSign Connector.
04Official documentation
→Related errors
- HTTP:UNAUTHORIZEDHTTP:UNAUTHORIZED means the server rejected the HTTP Request operation because authentication failed or was not provided (HTTP 401). Send the credentials the server expects, and handle the error type if a rejected call is something the flow should survive.
- HTTP:SECURITYHTTP:SECURITY means the authentication of the HTTP requester failed. Check the authentication settings and credentials on the HTTP Request configuration.
Test every fix in a non-production environment before you apply it to production. See how entries are verified.
More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer