API Reference - Ideal Postcodes vs OpenPLZ API
If you need a Geocoding API that's easy to integrate, go with OpenPLZ API.
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 ...
OpenPLZ API
A public street and postal code directory for Austria, Germany, Liechtenstein and Switzerland via an open REST API
API Reference - Ideal Postcodes
- Simple API key authentication
- HTTPS supported
OpenPLZ API
- No authentication required
- HTTPS supported
- CORS enabled for frontend use
| Feature | API Reference - Ideal Postcodes | OpenPLZ API |
|---|---|---|
| Authentication | apiKey | None |
| HTTPS | Yes | Yes |
| CORS | Unknown | Yes |
When to use which?
OpenPLZ API is the better choice for quick prototypes and hackathons since it requires no authentication. OpenPLZ API works directly from the browser with CORS enabled, making it better for frontend-only apps.