Loading…
Loading…
Add VIA's Maadi logistics layer to your store, marketplace, or operations stack — read your usage, register webhooks, and receive signed events for every status change. (Orders & inventory APIs coming soon.)
Sandbox-first · production keys after review
A deliberately small surface. Everything else — dispatch, assignment, OTP proof — is VIA's job.
Sign up and grab sandbox keys from the developer portal — test keys from day one.
Your first key-authenticated call: GET /v1/usage/current-month returns your call count, quota, and latency.
POST /v1/webhooks with a webhooks:manage key, and subscribe to order.*, driver.*, and payment.* events.
Every event lands on your endpoint, HMAC-signed, with retries on failure. Monitor usage from the portal.
Creating orders and syncing inventory directly over the API is on the roadmap. Available today: usage + webhooks. We'll notify developers before launch.
Your call count, included quota, and p50/p99 latency — read anytime with the tenants:read scope.
Creating orders and syncing inventory over the API is planned — not available with an API key yet.
Register your HTTPS endpoint and subscribe to the events you care about.
order.created → driver.assigned → order.status_changed → order.delivered, with retries.
driver.assigned and driver.location_updated, plus OTP-verified proof of delivery per order.
Handled through partner support today — refund status still lands on your webhook endpoint (refund.created, refund.approved).
Full API with test data — no real riders, no real charges.
Live keys issued after integration review.
A real engineer checks your webhook handling, retries and edge cases before go-live.
per month, billed annually
per month, billed annually
per month, billed annually
Maadi, Cairo — today. New zones open as VIA's own operations expand; partners are notified before launch.
Yes — every account gets both live and sandbox API keys. Sandbox keys are isolated from your live traffic and billing, so you can build against the usage and webhook APIs safely before you go live.
Yes. Subscribe to 28 event types including order.status_changed, driver.location_updated, and payment.captured. Signed HMAC-SHA256 payloads with automatic retry on failure.
Start against the sandbox, then request production access from the developer portal. We check your webhook handling and error paths before enabling live keys.
Plan pricing is listed above. Enterprise and custom terms are agreed during onboarding — talk to sales for anything beyond the standard tiers.
No — we return honest ETA windows per order instead of fixed promises. SLAs, if any, are agreed per contract.
Tell us about your business and volume. We'll set you up with sandbox keys and a real integration engineer.
View Developer Portal(approved partners only)