Public APIs / Geocoding / Checks
Checks API
NOTE: This is a preview of the API and it is not considered stable since refinements are still being made. Welcome to the Truora Check RESTful API reference. You may also want to check out our Validations API docs or our Signals API docs.
Open the Checks documentation Build something with it
Key facts
Authentication is described in the provider's OpenAPI spec and documentation. Most need a key or OAuth.
What you could build with Checks
Geocoding APIs turn addresses into coordinates and back, and give countries, regions and IP locations.
- Address autocomplete in checkout
- Delivery zones and routing
- Store locator on your website
OpenAPI spec
Checks has a machine-readable OpenAPI definition. Load it into Postman, Insomnia or a code generator to get every endpoint and a typed client in minutes.
How we would integrate Checks
- Generate a typed client from the OpenAPI spec, so every endpoint and field is checked at build time.
- Sign up with the provider, get a key and store it on the server in an env.php or secret store.
- Put a small backend in front of it, so the browser talks to your server and your server talks to the API.
- Cache results in your own database, so pages stay fast and you stay inside rate limits.
- Add monitoring: if the API goes down or changes, you get an alert before your customers notice.
Questions about Checks
Does the Checks API need an API key?
Authentication is described in the provider's OpenAPI spec and documentation. Most need a key or OAuth.
Is there an OpenAPI (Swagger) spec for Checks?
Yes. The spec is linked on this page, so you can generate a client or import it into Postman.
Can I call Checks from the browser?
It is not documented. Plan for a small server-side proxy to be safe.
Does Checks support HTTPS?
Yes, it is served over HTTPS.
Can you build an app with Checks for me?
Yes. FullStack Partner has developers who build and run products on APIs like this one. Send us a few lines and we reply with a plan and a fixed price.