FAQ

Why can't I send an offer through the API?

It's a product decision, not a forgotten technical limitation: in batch 1, offering stays site-only. See Product rules.

Why don't I get the client's phone number after an offer is accepted?

You never get it through the API or a webhook, in any batch. The number appears to both sides only in the site, at acceptance. It's a deliberate decision: a webhook lands in a system with other users and other retention policies that we don't control.

Can I download every listing published on a route?

Not all at once: lists go page by page, with caps. For continuous sync, wait for webhooks (batch 3) — don't build a scraper on top of pagination, it hits limits fast.

How do I know when a trip's stage changed?

For now, by re-reading GET /listings/{ref} — the transportStage field changes when the carrier taps it in the site. The listing.stage_changed webhook is planned.

My key was refused with 401, but it worked yesterday

Check: you didn't revoke it by mistake, it hasn't expired, the company or account aren't suspended, the plan still includes the API. The error code deliberately doesn't say which of these applies.

Do you have an official SDK?

Not yet. The examples in the documentation (cURL, Node) are executable and tested. A TypeScript client generated from OpenAPI may follow once the contract stabilizes.

Can I republish the data in an aggregator?

Not without a separate agreement. Public presentation through the API doesn't grant export or full republishing rights.