Skip to main content
For comprehensive error handling documentation, see the API Introduction - Error Handling section. This article covers the most common scenarios.

​
Most Common Issue: 422 Errors

A 422 error typically means you’re missing a required parameter—usually a geo_id. Solution: Resolve your address first using the Address Search endpoint, then use the returned geo_id in your permit query. See 422 error explained for details.

​
Empty Results vs Errors

An empty items array with a 200 response is not an error—it means your query was valid but no matching data exists. 
{
  "items": [],
  "total": 0
}

​
Quick Reference

CodeMeaningAction
200Success (may be empty)Check items array
400Bad requestReview request format
401UnauthorizedCheck API key
422Missing/invalid parameterSee 422 guide
500Server errorContact [email protected]

​
Full Documentation

For complete error handling details, response code explanations, and troubleshooting tips, see: