2xx response means your request succeeded. A 4xx response means something is wrong on your end — an invalid key, insufficient plan, or exhausted quota. A 5xx response indicates a server-side issue. The table and guidance below cover the errors you’re most likely to encounter.
Error code reference
Debugging checklist
If a request fails, work through these steps before contacting support:1
Check the X-API-Key header
Confirm the header name is spelled exactly
X-API-Key (case-sensitive in some clients) and that its value is your full key, including the dh_live_ prefix.2
Verify the key is active
If you recently rotated your API key, the old key is permanently invalidated. Retrieve your current key from Settings → API Keys or call
GET /api/user/api-key with a valid key. Update every integration that uses the old value.3
Confirm your plan includes API access
Open your account dashboard and check your active plan. API access is only available on Business (63.99/mo). If you’re on the Blogger plan, upgrade before retrying.
4
Check your monthly quota
Go to the dashboard and review your remaining upload and post quota for the current billing period. If the counter is at zero, your requests will be rejected with
429 until the period resets.Monitoring your quota
Server errors (5xx)
A
5xx response means the error originated on Dohoo’s servers, not in your request. Retry the request using exponential backoff — wait 1 second before the first retry, 2 seconds before the second, 4 seconds before the third, and so on. If the problem persists after several attempts, contact Dohoo support with the request details and the timestamp of the failure.