Errors

This page documents common API errors returned by the Metafide platform.

Code	Name	Description	Fix
400	Bad Request	The request was malformed or missing required parameters.	Check your request body and ensure all required fields are present.
401	Unauthorized	Missing or invalid API key.	Ensure you are passing a valid API key in the x-api-key header.
403	Forbidden	You do not have permission to access this resource.	Check your account permissions or contact support.
404	Not Found	The requested resource does not exist.	Verify the endpoint URL and resource ID are correct.
409	Conflict	A conflicting request was made, such as exceeding the 10-position limit per game or submitting a duplicate position.	Check your position count for the current game. Each user can place up to 10 positions per game.
422	Unprocessable Entity	The request was valid but contained invalid values.	Review the field values in your request and correct any invalid inputs.
429	Too Many Requests	You have exceeded the rate limit.	Wait before retrying. See Rate Limiting below.
500	Internal Server Error	An unexpected error occurred on the server.	Try again later. If the issue persists, contact Metafide support.
503	Service Unavailable	The server is temporarily unavailable or under maintenance.	Wait and retry. Check the Metafide status page for updates.

Rate Limiting

The Metafide API enforces rate limits to ensure fair usage and platform stability. If you exceed the allowed number of requests, you will receive a 429 Too Many Requests response.

Best Practices

• Throttle your requests — avoid sending bursts of rapid requests in quick succession.
• Cache responses — for data that doesn't change frequently (e.g. game schedules), cache responses locally instead of polling repeatedly.
• Use exponential backoff — when you receive a 429 response, wait progressively longer between retries (e.g. 1s, 2s, 4s, 8s).
• Poll at reasonable intervals — for live data like prices and game status, polling once per second is generally sufficient.