If you're using an API to integrate the feed with an external application, follow these steps to ensure everything is set up correctly:
1. Verify API keys
Ensure that your API keys are properly set in your app. You can generate and manage API keys in your Account Settings: https://rss.app/account/api.
2. Verify your query
Ensure that your query is formatted properly by referring to our API Documentation.
3. Common HTTP errors
400 - Bad Request
What it means: The request was unacceptable, often due to missing a required parameter or incorrect data.
What to do:
Double-check the request to ensure all required parameters are included.
Verify that the data you are sending matches the expected format (e.g., correct data type or required fields).
Review the API documentation to ensure your request is correctly structured.
401 - Unauthorized
What it means: No valid API key was provided, or the API key is incorrect.
What to do:
Ensure you are using the correct API key.
Check that the API key is properly included in the request header or URL.
If necessary, regenerate a new API key in your account settings.
402 - Request failed
What it means: The parameters were valid, but the request failed due to an issue on our end.
What to do:
Review the request parameters to confirm they are correct.
Wait for a few moments and try again in case of a temporary issue.
If the error persists, contact support with the request details.
403 - Forbidden
What it means: The API key doesn't have permission to perform the requested action.
What to do:
Check that the API key you’re using has the necessary permissions for the action you’re trying to perform.
If you are using an account with limited permissions, ensure your account has the correct access level. API access is only available with Pro Plans.
If you're unsure about permissions, review your account settings or reach out to support.
404 - Not found
What it means: The requested resource doesn’t exist.
What to do:
Verify that the URL endpoint you're trying to access is correct.
Ensure the resource you're requesting (e.g., a specific feed or data point) exists.
If you're trying to access a specific resource, make sure its ID or identifier is correct.
409 - Conflict
What it means: The request conflicts with another request (for example, using the same idempotent key).
What to do:
If you are using an idempotent key (to ensure a request is only processed once), verify that the key is unique.
Ensure there are no conflicting operations or duplicate requests being sent.
429 - Too many requests
What it means: You’ve sent too many requests in a short period.
What to do:
We have a 1 request per second rate limit per operation. Implement exponential backoff to slow down the rate of requests. This means gradually increasing the time between retry attempts.
Consider batching requests to reduce the number of API calls.
500, 502, 503, 504 - Server errors
What it means: Something went wrong on RSS.app’s end. These errors are rare and typically indicate server-side issues.
What to do:
Wait a few moments and try again. These errors are often temporary and may resolve on their own.
If the error persists for an extended period, contact support with the error details.
Still have questions? Reach out to our support team for further assistance.