Skip to content
العربيةGet started
Developers

Clear APIs, explicit boundaries.

Start with examples, then move to the API reference. Bardiya shows what exists and labels what still needs a preview or roadmap.

AvailableAuthorization · JSON · RESTEgypt coverage
Developer path

Three steps, no noise.

01Available

Start in the Playground

Read static Search, Routes, and Maps examples before opening a project or writing an integration.

Open the Playground ↗
02Available

Build on the public API

Review current endpoints, coverage, and request/response shapes before committing.

API reference ↘
03Available

Talk through the use case

When you need a custom workflow, we define the path instead of promising a product that does not exist.

Talk to us ↗
API reference

The right start is a clear contract.

The current reference covers map tiles, places, geocoding, and directions. Tracking has its own surface and is available as RC1.

Test the example
GET /v1/places/search
# Current public maps surface
curl https://api.bardiya.com/v1/places/search \
  -H "Authorization: Bearer YOUR_API_KEY" \
  --data-urlencode "q=القاهرة"