Booking sender and receiver
Endpoints
Section titled “Endpoints”| Method | Path | Description |
|---|---|---|
GET | /api/bookings/v4/{id}/sender | Sender (pickup) address |
GET | /api/bookings/v4/{id}/receiver | Receiver (delivery) address |
Requires authentication. Booking must belong to the member.
Response
Section titled “Response”Each endpoint returns an address object (same fields as on the booking payload):
| Field | Type | Description |
|---|---|---|
id | integer | Address id |
name | string | Contact name |
company_name | string | Company |
email | string | |
phone | string | Phone |
address | string | Street line |
suburb | string | Suburb |
postcode | string | Postcode |
state | string | State |
type | string | business or residential |
country | string | Country code |
To update addresses, use update a booking with a sender / receiver object rather than these GET routes.
PATCH booking
Section titled “PATCH booking”PATCH /api/bookings/v4/{id}Also exists as a partial-update alias of the booking update flow (same auth rules as PUT). Prefer PUT with the fields you need for new integrations unless you already depend on PATCH.