Skip to content
PubIndexAPI

Errors & Troubleshooting

This page provides a comprehensive list of error codes, their meanings, and suggestions on how to troubleshoot and resolve common issues encountered while using the Publisher Indexing API.

Missing Feed Parameter Error

  • Error code: 400
  • Description: Missing feed parameter.
  • Possible cause: The API request is missing the required feed parameter.
  • Solution: Ensure that you include the feed parameter in your API request.

Invalid Feed Parameter Error

  • Error code: 400
  • Description: Invalid feed parameter.
  • Possible cause: The API request contains an invalid feed parameter.
  • Solution: Verify that the feed parameter value is a valid URL.

Invalid API Key Error / Unauthorized Access

  • Error code: 401
  • Description: Invalid API key.
  • Possible cause: The API request contains an invalid API key.
  • Solution: Check you are including the full API key in the request. If you don’t have an API key, please register for an account and select a subscription plan. If you are having difficulties with an existing key you can contact support.
{ 
    "statusCode": 401, 
    "message": "Access denied due to invalid subscription key. Make sure to provide a valid key for an active subscription." 
}

Payload Too Large

  • Error code: 413
  • Description: Payload Too Large
  • Possible cause: The response size of the feed exceeds the allowed limit (10MB).
  • Solution: Use an RSS feed or sitemap below 10MB in size.

Fetch Error

  • Error code: 500
  • Description: Error fetching feed size or Google APIs.
  • Possible cause: There was an error while fetching the specified feed or communicating with Google APIs.
  • Solution: Check your feed URL and make sure it’s accessible. If the issue persists, it might be a temporary issue with the Google APIs. If everything else is working correctly you can check your server logs to make sure the fetch request is not being blocked by your firewall.