Opencage · Geo

OpenCage Geocoding API / request a JSON geocoding response

Geocode (JSON)

Private Gateway connection

Data below comes from the configured private Gateway. Provider activation remains governed by its evidence and policy gates.

unverifiedRequest shape unavailableUnverified

Published API evidence

Public metadata only. Response bodies, credentials, and internal review notes are never displayed.

No verification date is claimed. No response capture is claimed.

Request parameters

abbrv query · optional
1 or 0 (OpenCage's actual wire format; its OpenAPI spec declares this as boolean but the live API rejects true/false and expects an integer).
add_request query · optional
1 or 0 (OpenCage's actual wire format; its OpenAPI spec declares this as boolean but the live API rejects true/false and expects an integer).
address_only query · optional
1 or 0 (OpenCage's actual wire format; its OpenAPI spec declares this as boolean but the live API rejects true/false and expects an integer).
bounds query · optional
decimal coordinates in min long, min lat, max long, max lat order. Example: "-0.563160,51.280430,0.278970,51.683979"
countrycode query · optional
Example: "de"
language query · optional
the preferred language of results. Example: "de"
limit query · optional
Example: 1
no_annotations query · optional
1 or 0 (OpenCage's actual wire format; its OpenAPI spec declares this as boolean but the live API rejects true/false and expects an integer).
no_dedupe query · optional
1 or 0 (OpenCage's actual wire format; its OpenAPI spec declares this as boolean but the live API rejects true/false and expects an integer).
no_record query · optional
1 or 0 (OpenCage's actual wire format; its OpenAPI spec declares this as boolean but the live API rejects true/false and expects an integer).
pretty query · optional
1 or 0 (OpenCage's actual wire format; its OpenAPI spec declares this as boolean but the live API rejects true/false and expects an integer).
proximity query · optional
Latitude and longitude decimal coordinates to bias results toward. Example: "52.3877830, 9.7334394"
q query · required
Location to geocode - can be an address, place name, or decimal coordinates in latitude, longitude order. Example: "52.5432379, 13.4142133"
roadinfo query · optional
1 or 0 (OpenCage's actual wire format; its OpenAPI spec declares this as boolean but the live API rejects true/false and expects an integer).

Provider docs How to run it