API Reference - Ideal Postcodes vs bng2latlong
If you need a Geocoding API that's easy to integrate, go with bng2latlong.
API Reference - Ideal Postcodes
# Getting Started ## Overview ### Access All API methods are either a `GET`, `POST` or `OPTIONS` request. The API communicates over both HTTPS and plain HTTP using IPv4 and IPv6. We recommend ...
bng2latlong
Convert British OSGB36 easting and northing (British National Grid) to WGS84 latitude and longitude
API Reference - Ideal Postcodes
- Simple API key authentication
- HTTPS supported
bng2latlong
- No authentication required
- HTTPS supported
- CORS enabled for frontend use
| Feature | API Reference - Ideal Postcodes | bng2latlong |
|---|---|---|
| Authentication | apiKey | None |
| HTTPS | Yes | Yes |
| CORS | Unknown | Yes |
When to use which?
bng2latlong is the better choice for quick prototypes and hackathons since it requires no authentication. bng2latlong works directly from the browser with CORS enabled, making it better for frontend-only apps.