Developer Center›Troubleshooting

    Troubleshooting

    Current troubleshooting notes for the implemented backend routes.

    401 Unauthorized

    • Verify the API key is active and not revoked.
    • Use Authorization: Bearer YOUR_API_KEY or x-api-key for public `/api/v1` routes.
    • POST /api/v1/data-deletion currently expects x-api-key.
    • If a webhook or dispute request returns 401, confirm you sent the key on the `/api/v1/...` route rather than the dashboard-only internal route.

    207 Partial Success

    POST /api/v1/submit-metro2-data uses 207when some records were accepted and some failed validation or save logic.

    • Inspect the response errors array for failing record indexes.
    • Use test keys for dry runs instead of assuming a separate sandbox hostname.
    • Prefer ISO dates like 2025-03-01 in public payloads.

    429 Rate Limit Exceeded

    • submit-metro2-data: 300 requests / minute
    • files/upload-url: 60 requests / minute
    • files/{id}/process: 120 requests / minute
    • integrations/rentvine/sync: 10 requests / minute
    • Use the response body's retry_after value before retrying.

    Unsupported Assumptions

    • Do not use `https://api.metro2reporting.com` or `https://sandbox-api.metro2reporting.com` as the documented hostnames.
    • Do not assume a separate public sandbox hostname; live and test traffic use the same host.
    • Do not use the internal dashboard routes when the public equivalent exists under /api/v1.