OAuth 1.0.A Authorization Error Codes
Errors can occur during authorization. For example, the callback URL is invalid. When errors occur during the OAuth 1.0.A flow, Salesforce returns an error code.
Required Editions
| Available in: both Salesforce Classic and Lightning Experience |
| Available in: All Editions |
To help troubleshoot why an error occurred, review the following error code descriptions.
| Fault Code | Error | Notes |
|---|---|---|
| 1701 | Failed: Nonce Replay Detected | A nonce can only be used once. |
| 1702 | Failed: Missing Consumer Key Parameter | The oauth_consumer_key parameter isn’t
provided. |
| 1703 | Failed: Invalid Access Token | The access token is invalid. |
| 1704 | Failed: Version Not Supported | The required version for the oauth_version
parameter is 1.0. |
| 1705 | Failed: Invalid Timestamp | The timestamp can be missing, in the future, too old, or malformed. |
| 1706 | Failed: Invalid Nonce | The nonce is missing. |
| 1707 | Failed: Missing OAuth Token Parameter | The oauth_token parameter is
missing. |
| 1708 | Failed: IP Address Not Allowed | The IP address is restricted or called during invalid login hours. |
| 1709 | Failed: Invalid Signature Method | The request token contains an invalid oauth_signature_method parameter. |
| 1710 | Failed: Invalid Callback URL | The request token contains an invalid oauth_callback
parameter. Value must be either oob or a valid URL
that uses https. |
| 1711 | Failed: Invalid Verifier | The access token. contains an invalid oauth_verifier
parameter. |
| 1712 | Failed: Get Access Token Limit Exceeded | The connected app attempted to exchange a request token for an access token three times. |
| 1713 | Failed: Consumer Deleted | The connected app has been deleted from the Salesforce org. |
| 1716 | Failed: OAuth Api Access Disabled | Either the Lightning Platform web services API isn’t enabled for the org, or OAuth API access has been disabled for the org. |
Did this article solve your issue?
Let us know so we can improve!
