Hızlıyo DevelopersSend an order, a courier picks it up

Integrate your POS with Hızlıyo's courier network. Five endpoints, one webhook.

Five endpoints

Token, stores, orders, order status, cancellation. Fleet discovery comes back inside the store response — no extra call.

Synchronous accept or reject

We answer before the request returns. If no courier is available, you know immediately instead of finding out twenty minutes later.

Sandbox before production

A test key gives you fake fleets, fake couriers and a sixty-second delivery. No real courier leaves the restaurant.

What this is

Your point-of-sale software sends a delivery request to Hızlıyo. A courier company that works with Hızlıyo picks the package up from the restaurant and delivers it to the customer. You receive status updates as they happen.

The restaurant does not need a Hızlıyo account. It keeps using your POS.

What this is not

Hızlıyo is a software provider, not a carrier. The delivery is performed by the courier company (the fleet) that the restaurant has an agreement with. Pricing, invoicing and collection happen between the restaurant and the fleet — Hızlıyo is not a party to that.

Status updates we send are informational. They tell you what our system knows; they are not a delivery guarantee.

Before you write code

You need three things:

Credentials — a client id and secret. Sandbox credentials are issued first; production credentials come after the launch checklist.
A store — each restaurant branch is registered once with its tax number, address and pickup coordinates. See Stores.
A fleet — the restaurant agrees with a courier company, and you record that choice on the store. Until a fleet is attached, the store cannot receive orders.

Start with Getting started.