# Own Network Deliveries

Rendr's Own Network solution allows stores to fulfil deliveries using their own staff or internal courier network. Deliveries are created via the standard endpoint with additional fields to assign a staff courier.

***

## Create a Delivery with a Staff Courier

Use the standard Create Delivery payload with `use_staff_couriers: true` and a `staff_courier` object identifying the assigned driver.

```
POST {{domain}}/{{tenant_id}}/deliveries
```

**Authentication:** Bearer token required via the `Authorization` header.

```json title="POST /{{tenant_id}}/deliveries — Own Network"
{
    "store_id": "rendr-test",
    "reference": "myorder-001",
    "ready_for_pickup_at": "2026-02-04T11:21:13+11:00",
    "use_staff_couriers": true,
    "staff_courier": {
        "phone": "+61400000000",
        "driver_name": "John Smith",
        "driver_id": "ABC123"
    },
    "address": { ... },
    "customer": { ... },
    "parcels": [ ... ]
}
```

<Note>
  `use_staff_couriers` must be `true` and the `staff_courier` object is required to assign the delivery to a staff member. If the driver is new, they will be automatically added to the store's staff courier list on first assignment.
</Note>

### `staff_courier` Fields

| Field         | Type   | Required | Description                                                                                                       |
| ------------- | ------ | -------- | ----------------------------------------------------------------------------------------------------------------- |
| `phone`       | String | Yes      | The driver's mobile number in E.164 format (e.g. `+61400000000`). Used for SMS notification and driver app login. |
| `driver_name` | String | Yes      | The full name of the staff courier.                                                                               |
| `driver_id`   | String | No       | An internal identifier for the driver in your system.                                                             |

***

## Courier SMS Notification

Once a delivery is created and assigned, the staff courier receives an SMS with pickup and delivery details and a link to accept the job via the Rendr Driver App. No app installation is required — drivers log in using phone number verification.

**Driver App URLs:**

| Environment | URL                                      |
| ----------- | ---------------------------------------- |
| UAT         | `https://driver-app-uat.vercel.app/jobs` |
| Production  | `https://driver.rendr.delivery/jobs`     |

***

## Retrieve Staff Couriers

To list existing staff couriers for a tenant — useful for building courier selection UIs — use the following endpoint:

```
GET {{domain}}/{{tenant_id}}/staff-couriers?page=1
```

**Authentication:** Bearer token required via the `Authorization` header.

This returns paginated staff courier profiles that can be used to populate a courier selection dropdown or manage existing drivers.

***

## Interface Recommendations

When a user selects "Own Network" in your interface, prompt them to either:

* **Select an existing courier** — using data from `GET /staff-couriers`, or
* **Enter a new staff member's name and phone number** — they will be added to the store's courier list automatically on first delivery.

The delivery creation workflow is identical in both cases.

***

For a full walkthrough of the driver experience, see the [Own Network Deliveries](https://rendr.zendesk.com/hc/en-au/articles/10967810040719-Own-Network-Deliveries) guide.