🗺️ Maps API Documentation
Evegram Secure Gateway v1.0
The Evegram Maps API provides global geographic services powered by OpenStreetMap (OSM) and distributed via Protomaps. Our infrastructure covers the entire planet and is optimized for the MapLibre engine.
🔐 Authentication & Security
Access is regulated via a unique Client API Key generated in your Hub OS.
Security Best Practices
- Backend Proxy: We strongly recommend routing API calls through your own backend. This prevents your API Key from being exposed in the client-side source code.
- Domain Whitelisting: Always configure your Allowed Domains (CORS) or Mobile Bundle IDs in the Hub OS dashboard to prevent unauthorized usage.
Required Headers
| Header | Description |
|---|---|
x-api-key | Your Client API Key. |
x-bundle-id | (Optional) The Bundle ID for Mobile requests. |
🎨 Map Styles
All styles are served as Vector Tiles (MVT).
| Theme ID | HUD Name | Best For |
|---|---|---|
evegram_light_it | Day | Outdoor/Bright environments. |
evegram_night_it | Night | Battery saving & eye comfort. |
evegram_silver_it | Silver | Corporate & Minimalist UI. |
evegram_vintage_it | Vintage | Vintage UI. |
evegram_mobile_day | Vintage | For Mobile Day UI. |
evegram_mobile_night | Vintage | For Mobile Night UI. |
Example URL (New York View):
https://apimaps.evegram.org/styles/evegram_night_it.json?key=YOUR_API_KEY