Transfer company walk-through · Step 7 of 7 · Optional
The offer flowreceive, accept or decline
Sample data. Nothing is sent to Transferz.
Why this step exists
Some companies get journeys as offers instead of direct assignments. Transferz sends offerCreatedEvent; you accept it, with a meeting point, or decline it with a reason before it expires.
Accepting returns the journey, which then continues as in the steps before.
The event arrives
Your endpoint · https://example.com/webhooks/transferz
Sample eventsNo events yet. Run the step and the event arrives here, as your endpoint would receive it.
Sample data · nothing is sent
What do you answer?
Take the journey and choose where the driver meets the traveller.
Accept the offer
This step has not been run yet, so this uses the sample offer and meeting point. Run step 7 to use your own.
Accept the offer
curl --request POST \ --url 'https://warpdrive.staging.transferz.com/transfercompanies/offers/6120044/accept' \ --header 'Accept: application/json' \ --header 'Content-Type: application/json' \ --header 'X-Request-ID: req-ams-0002' \ --header 'X-API-Key: YOUR_STAGING_API_KEY' \ --data '{ "meetingPointId": 2561, "type": "HUB"}' Sample data · nothing is sent
Common pitfall
Offers expire (see expiry). Accepting late fails with OFFER_EXPIRED or OFFER_MISSED, and when meetingPointRequired is true you must send one of the offered meeting points.
Ready to do this for real?
Sign in with the staging account Transferz set up for you. Then run the same calls against staging with your own key.