Operated by Geodefender
From your use case to the first lookup
Learn how to request APINITRO access, confirm coverage and commercial terms and prepare your first integration.
1. Define what you need
Explore the catalog and use cases. Send a description of your project from a product page or the contact form; enquiry links include the relevant API, article or topic context.
2. Confirm scope and terms
We review coverage, required inputs, intended usage and commercial terms with you. Pricing depends on the agreed scope. Sending the form does not incur charges or enable access automatically.
3. Prepare your organization
Once access is confirmed, use the portal for your organization and enabled permissions. Review the product reference, environments, authentication, limits and billing terms with the team before integrating. Store credentials in your backend.
4. Verify a complete lookup
An asynchronous integration has three stages: submit the request, poll its status or receive a webhook, and interpret the result. An accepted request is not yet a completed result.
Test with authorized data and retain the request reference. Check which sources responded, which failed and how to retry without duplicating work. Distinguish an empty result from a partial one.
Before going live
Activation timing is confirmed when your case is reviewed. If you already have access, select Sign in at the top of the page; if you need help, describe the issue in the form without including credentials.
- Required inputs and agreed product coverage.
- Authentication and permissions for your environment.
- States, errors and idempotent retries.
- Webhook reception and validation, where applicable.
- Agreed pricing, usage, support and service terms.
Example: integrating a traffic-fine lookup
A team managing vehicles first defines the country and jurisdictions it needs to check. Before development, confirm which sources are enabled for its organization, the identifiers each source requires and the authorization to use them.
The illustrative flow is: submit an authorized lookup, retain its reference, wait for the result and review coverage for each source. An unavailable source does not mean the vehicle has no fines. Results should retain their date and scope; they do not replace an official certificate.
Interpreting the information
- Accepted request: the request was received and may still be pending.
- Complete result: the enabled scope was processed. This does not imply nationwide coverage.
- Partial result: some sources responded and others did not; preserve this distinction.
- No records: the sources consulted returned no results for the supplied inputs.
- Error or unavailable source: review the cause and retry policy before repeating the request.
Using AI assistants
The website provides public HTML and Markdown content. An assistant can read product pages and guides to evaluate an integration; this grants no access to APIs or customer data. An operational MCP connection requires confirmed availability, authorization and specific permissions.