BelliBelliUse X-Belli-Token or Authorization: Bearer TOKEN. Tokens are managed from the Belli admin or customer portal, while customer settings prepare domains, webhooks, team contacts, and future integrations.
curl -H "X-Belli-Token: YOUR_TOKEN" "https://belli.ip.mr/api/search?q=Ksar"Keep tokens server-side where possible. For embedded maps, use short-lived page contexts and domain controls as BELLI matures.
{ "ok": true, "results": [...] }Clients should tolerate extra fields so BELLI can add richer geospatial intelligence without breaking apps.
Current stable API surface for ecommerce, delivery, and future mobility workflows.
Tenant status, quota, usage, and enabled service details.
List tenant private places, or POST a corrected delivery landmark.
Search local and fallback map data.
Fast suggestion endpoint for search fields.
Search with optional origin and distance scoring.
Nearest local Belli places around a driver or customer.
Find nearest known Belli place.
Estimate distance/duration and external navigation links.
Simple nearest-first ordering for delivery stops.
Quote zone coverage, delivery fee, and ETA for checkout.
Find the nearest active branch for a customer coordinate.
Expose curated operational place lists to apps and teams.
Embedded driver map for webviews.
const res = await fetch("/api/search?q=Ksar", { headers: { "X-Belli-Token": token } });
const data = await res.json();https://belli.ip.mr/map?token=YOUR_TOKEN&to=18.0735,-15.9582&label=DeliveryThis action changes the operational state of BELLI.