406 response on IPinfo API services: Malformed access token

Docs Knowledgebase
,
1

If you get a 406 response when you try to access our services, that may indicate you have inputted an incorrect or malformed IPinfo access token.

The 406 response is returned to an API request if the IPinfo access token you used is incorrect or malformed. Before you contact your support team, confirm that the access token you provided to the API is correct.

A common pattern we see is adding spaces after the token API parameter. When you add a space after the ?token=, it creates a malformed access token as URL encoding converts spaces to “%20”. For example:

curl "https://ipinfo.io/json?token=%20<YOUR_TOKEN>"
{"error": 406, "data": "If you believe you've received this request in error, please open a support request."}

So, kindly review your IPinfo API request URL. If you are unsure about API authentication, here is the documentation: https://ipinfo.io/developers#authentication

If you are not using an IPinfo access token, or you have confirmed that you have used your IPinfo access token appropriately and are still getting a 406 response, we then recommend you reach out to our support team. In the process of reaching out to our support team, we recommend you provide the following information as context:

  • Date and time when you made the API request.
  • IPinfo access token, if available
  • Output of:
    • curl -v https://ipinfo.io
    • curl -v https://ipinfo.io?token=<YOUR_TOKEN>