From 5b02524aa97a7415adcfe16f324112fa9ed0dee2 Mon Sep 17 00:00:00 2001
From: "Ronald A. Richardson" <me@ron.dev>
Date: Sun, 23 Aug 2026 21:18:11 +0800
Subject: [PATCH 1/2] feat(fleetbase-api): driver manifests and driver password
 endpoints
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Documents the consumable endpoints added in fleetops#304 and fleetops#305.

Drivers gains three password requests. A password change is an authorisation
decision rather than an attribute update, which is why it is not part of
PUT /drivers/:id — that endpoint no longer accepts a password at all. The
descriptions carry the two properties a caller needs to know about and cannot
discover by trying: the reset request answers identically whether or not the
identity exists, so it cannot be used to enumerate an organization's drivers,
and a wrong code, an expired code and an unknown identity all return the same
error.

A new Manifests folder covers the route a driver actually drives — a manifest is
an order-agnostic sequence of stops which may span several orders, or none the
driver has seen as an order. Retrieve returns the stops in sequence with their
places inline, so a route of twenty stops is one request rather than twenty-one.

The optimize description says plainly what it is: a nearest-neighbour walk over
road distances, usually a large improvement on an arbitrary order and not
guaranteed optimal, which reorders the stops of one assigned manifest rather
than allocating work across a fleet the way the orchestrator does. Completed and
skipped stops keep their place.

Listing a driver's manifests sits with the other driver-scoped requests rather
than in the new folder, next to List Driver Organizations.

No response examples yet: the endpoints are still in review on the fleetops
release branch, and an example recorded against an unmerged branch would be a
guess rather than verified behaviour. Happy to add them once merged.

npm run postman:lint — 196 requests scanned in Fleetbase API, 0 errors,
0 warnings.
---
 package-lock.json                             | 13 +++++++++
 .../Change Driver Password.params.yaml        | 18 ++++++++++++
 .../Change Driver Password.request.yaml       | 26 +++++++++++++++++
 .../List Driver Manifests.queryParams.yaml    | 14 ++++++++++
 .../List Driver Manifests.request.yaml        | 16 +++++++++++
 .../Request Driver Password Reset.params.yaml |  6 ++++
 ...Request Driver Password Reset.request.yaml | 19 +++++++++++++
 .../Drivers/Reset Driver Password.params.yaml | 14 ++++++++++
 .../Reset Driver Password.request.yaml        | 21 ++++++++++++++
 .../Manifests/.resources/definition.yaml      |  6 ++++
 .../Manifests/.resources/object.yaml          | 22 +++++++++++++++
 .../Manifests/Optimize a Manifest.params.yaml | 10 +++++++
 .../Optimize a Manifest.request.yaml          | 28 +++++++++++++++++++
 .../Retrieve a Manifest.request.yaml          | 14 ++++++++++
 .../Update a Manifest Stop.params.yaml        | 10 +++++++
 .../Update a Manifest Stop.request.yaml       | 23 +++++++++++++++
 16 files changed, 260 insertions(+)
 create mode 100644 package-lock.json
 create mode 100644 postman/collections/Fleetbase API/Drivers/Change Driver Password.params.yaml
 create mode 100644 postman/collections/Fleetbase API/Drivers/Change Driver Password.request.yaml
 create mode 100644 postman/collections/Fleetbase API/Drivers/List Driver Manifests.queryParams.yaml
 create mode 100644 postman/collections/Fleetbase API/Drivers/List Driver Manifests.request.yaml
 create mode 100644 postman/collections/Fleetbase API/Drivers/Request Driver Password Reset.params.yaml
 create mode 100644 postman/collections/Fleetbase API/Drivers/Request Driver Password Reset.request.yaml
 create mode 100644 postman/collections/Fleetbase API/Drivers/Reset Driver Password.params.yaml
 create mode 100644 postman/collections/Fleetbase API/Drivers/Reset Driver Password.request.yaml
 create mode 100644 postman/collections/Fleetbase API/Manifests/.resources/definition.yaml
 create mode 100644 postman/collections/Fleetbase API/Manifests/.resources/object.yaml
 create mode 100644 postman/collections/Fleetbase API/Manifests/Optimize a Manifest.params.yaml
 create mode 100644 postman/collections/Fleetbase API/Manifests/Optimize a Manifest.request.yaml
 create mode 100644 postman/collections/Fleetbase API/Manifests/Retrieve a Manifest.request.yaml
 create mode 100644 postman/collections/Fleetbase API/Manifests/Update a Manifest Stop.params.yaml
 create mode 100644 postman/collections/Fleetbase API/Manifests/Update a Manifest Stop.request.yaml

diff --git a/package-lock.json b/package-lock.json
new file mode 100644
index 0000000..59dc90b
--- /dev/null
+++ b/package-lock.json
@@ -0,0 +1,13 @@
+{
+  "name": "@fleetbase/postman",
+  "version": "0.1.0",
+  "lockfileVersion": 3,
+  "requires": true,
+  "packages": {
+    "": {
+      "name": "@fleetbase/postman",
+      "version": "0.1.0",
+      "license": "Apache-2.0"
+    }
+  }
+}
diff --git a/postman/collections/Fleetbase API/Drivers/Change Driver Password.params.yaml b/postman/collections/Fleetbase API/Drivers/Change Driver Password.params.yaml
new file mode 100644
index 0000000..f365666
--- /dev/null
+++ b/postman/collections/Fleetbase API/Drivers/Change Driver Password.params.yaml	
@@ -0,0 +1,18 @@
+$kind: params
+fields:
+  - name: current_password
+    type: string
+    required: true
+    description: The driver's existing password. The change is refused without it.
+  - name: password
+    type: string
+    required: true
+    description: The new password. Must be at least 8 characters.
+  - name: password_confirmation
+    type: string
+    required: false
+    description: When present, must match `password`.
+  - name: device_name
+    type: string
+    required: false
+    description: Name for the replacement token issued to the caller. Defaults to `navigator`.
diff --git a/postman/collections/Fleetbase API/Drivers/Change Driver Password.request.yaml b/postman/collections/Fleetbase API/Drivers/Change Driver Password.request.yaml
new file mode 100644
index 0000000..2414aa6
--- /dev/null
+++ b/postman/collections/Fleetbase API/Drivers/Change Driver Password.request.yaml	
@@ -0,0 +1,26 @@
+$kind: http-request
+name: "Change Driver Password"
+description: |-
+  Changes the password of a driver who is signed in, proving the current one.
+
+  A password change is an authorisation decision rather than an attribute update, which is why it is not part of `PUT /drivers/:id` — that endpoint does not accept a password at all. Supplying the wrong `current_password` is refused and changes nothing.
+
+  Every other session is revoked when the password changes, and a fresh token is returned in the same response, so the caller keeps working while other devices are signed out.
+url: "{{base_url}}/{{namespace}}/drivers/:id/change-password"
+method: POST
+pathVariables:
+  - key: id
+    value: "{{driver_id}}"
+    description: (Required) The driver whose password is being changed.
+
+body:
+  type: json
+  content: |-
+    {
+      "current_password": "{{driver_current_password}}",
+      "password": "{{driver_new_password}}",
+      "password_confirmation": "{{driver_new_password}}",
+      "device_name": "navigator"
+    }
+
+order: 13000
diff --git a/postman/collections/Fleetbase API/Drivers/List Driver Manifests.queryParams.yaml b/postman/collections/Fleetbase API/Drivers/List Driver Manifests.queryParams.yaml
new file mode 100644
index 0000000..e871347
--- /dev/null
+++ b/postman/collections/Fleetbase API/Drivers/List Driver Manifests.queryParams.yaml	
@@ -0,0 +1,14 @@
+$kind: queryParams
+fields:
+  - name: status
+    type: string
+    required: false
+    description: Comma separated statuses to include, such as `pending,in_progress`.
+  - name: on
+    type: string
+    required: false
+    description: Only manifests scheduled on this date, as `YYYY-MM-DD`.
+  - name: limit
+    type: integer
+    required: false
+    description: Maximum manifests to return. Defaults to 30.
diff --git a/postman/collections/Fleetbase API/Drivers/List Driver Manifests.request.yaml b/postman/collections/Fleetbase API/Drivers/List Driver Manifests.request.yaml
new file mode 100644
index 0000000..4712fdf
--- /dev/null
+++ b/postman/collections/Fleetbase API/Drivers/List Driver Manifests.request.yaml	
@@ -0,0 +1,16 @@
+$kind: http-request
+name: "List Driver Manifests"
+description: |-
+  Lists the manifests assigned to a driver, newest first.
+
+  A manifest is a driver's route: an order-agnostic sequence of stops which may span several orders, or none the driver has seen as an order.
+
+  Defaults to a recent window rather than the driver's whole history. Use `status` and `on` to narrow it further.
+url: "{{base_url}}/{{namespace}}/drivers/:id/manifests"
+method: GET
+pathVariables:
+  - key: id
+    value: "{{driver_id}}"
+    description: (Required) The driver whose manifests to list.
+
+order: 13300
diff --git a/postman/collections/Fleetbase API/Drivers/Request Driver Password Reset.params.yaml b/postman/collections/Fleetbase API/Drivers/Request Driver Password Reset.params.yaml
new file mode 100644
index 0000000..256f89e
--- /dev/null
+++ b/postman/collections/Fleetbase API/Drivers/Request Driver Password Reset.params.yaml	
@@ -0,0 +1,6 @@
+$kind: params
+fields:
+  - name: identity
+    type: string
+    required: true
+    description: The driver's email address or phone number.
diff --git a/postman/collections/Fleetbase API/Drivers/Request Driver Password Reset.request.yaml b/postman/collections/Fleetbase API/Drivers/Request Driver Password Reset.request.yaml
new file mode 100644
index 0000000..824808a
--- /dev/null
+++ b/postman/collections/Fleetbase API/Drivers/Request Driver Password Reset.request.yaml	
@@ -0,0 +1,19 @@
+$kind: http-request
+name: "Request Driver Password Reset"
+description: |-
+  Sends a password reset code to a driver who cannot sign in.
+
+  The code goes by email or SMS depending on whether `identity` looks like an email address or a phone number.
+
+  The response is the same whether or not the identity belongs to a driver. That is deliberate: an endpoint that answered differently for an unknown number would be a way to enumerate an organization's drivers.
+url: "{{base_url}}/{{namespace}}/drivers/forgot-password"
+method: POST
+
+body:
+  type: json
+  content: |-
+    {
+      "identity": "{{driver_email}}"
+    }
+
+order: 13100
diff --git a/postman/collections/Fleetbase API/Drivers/Reset Driver Password.params.yaml b/postman/collections/Fleetbase API/Drivers/Reset Driver Password.params.yaml
new file mode 100644
index 0000000..da8fb06
--- /dev/null
+++ b/postman/collections/Fleetbase API/Drivers/Reset Driver Password.params.yaml	
@@ -0,0 +1,14 @@
+$kind: params
+fields:
+  - name: identity
+    type: string
+    required: true
+    description: The driver's email address or phone number — the same one the code was sent to.
+  - name: code
+    type: string
+    required: true
+    description: The verification code sent by `POST /drivers/forgot-password`.
+  - name: password
+    type: string
+    required: true
+    description: The new password. Must be at least 8 characters.
diff --git a/postman/collections/Fleetbase API/Drivers/Reset Driver Password.request.yaml b/postman/collections/Fleetbase API/Drivers/Reset Driver Password.request.yaml
new file mode 100644
index 0000000..90262f6
--- /dev/null
+++ b/postman/collections/Fleetbase API/Drivers/Reset Driver Password.request.yaml	
@@ -0,0 +1,21 @@
+$kind: http-request
+name: "Reset Driver Password"
+description: |-
+  Sets a new password using the code sent by `POST /drivers/forgot-password`.
+
+  A wrong code, an expired code and an unknown identity all return the same error, so the endpoint cannot be used to test which of the three happened.
+
+  Every session is revoked on success. A reset is a recovery from losing control of an account, so nothing that was signed in stays signed in.
+url: "{{base_url}}/{{namespace}}/drivers/reset-password"
+method: POST
+
+body:
+  type: json
+  content: |-
+    {
+      "identity": "{{driver_email}}",
+      "code": "{{driver_password_reset_code}}",
+      "password": "{{driver_new_password}}"
+    }
+
+order: 13200
diff --git a/postman/collections/Fleetbase API/Manifests/.resources/definition.yaml b/postman/collections/Fleetbase API/Manifests/.resources/definition.yaml
new file mode 100644
index 0000000..617546e
--- /dev/null
+++ b/postman/collections/Fleetbase API/Manifests/.resources/definition.yaml	
@@ -0,0 +1,6 @@
+$kind: collection
+description: |-
+  A manifest is a driver's route: an order-agnostic sequence of stops which may span several orders, or none the driver has seen as an order.
+
+  These endpoints are for the driver running the route. Creating, cancelling and deleting a manifest is dispatch work and is not part of the consumable API.
+order: 8500
diff --git a/postman/collections/Fleetbase API/Manifests/.resources/object.yaml b/postman/collections/Fleetbase API/Manifests/.resources/object.yaml
new file mode 100644
index 0000000..1a7ba5d
--- /dev/null
+++ b/postman/collections/Fleetbase API/Manifests/.resources/object.yaml	
@@ -0,0 +1,22 @@
+$kind: object
+name: Manifest
+description: |-
+  A route assigned to a driver for a day, made of ordered stops.
+example: |
+  {
+    "id": "manifest_7KpQ2Rx9Vz",
+    "status": "in_progress",
+    "scheduled_date": "2026-08-23",
+    "started_at": "2026-08-23T07:12:04.000000Z",
+    "completed_at": null,
+    "total_distance_m": 41200,
+    "total_duration_s": 5400,
+    "stop_count": 8,
+    "completed_stops": 3,
+    "pending_stops": 5,
+    "driver_name": "Ron",
+    "vehicle_name": "EAS-01",
+    "notes": null,
+    "updated_at": "2026-08-23T09:02:00.000000Z",
+    "created_at": "2026-08-23T06:40:00.000000Z"
+  }
diff --git a/postman/collections/Fleetbase API/Manifests/Optimize a Manifest.params.yaml b/postman/collections/Fleetbase API/Manifests/Optimize a Manifest.params.yaml
new file mode 100644
index 0000000..8f30b0d
--- /dev/null
+++ b/postman/collections/Fleetbase API/Manifests/Optimize a Manifest.params.yaml	
@@ -0,0 +1,10 @@
+$kind: params
+fields:
+  - name: latitude
+    type: number
+    required: false
+    description: The driver's current latitude. The walk starts here when both coordinates are given.
+  - name: longitude
+    type: number
+    required: false
+    description: The driver's current longitude.
diff --git a/postman/collections/Fleetbase API/Manifests/Optimize a Manifest.request.yaml b/postman/collections/Fleetbase API/Manifests/Optimize a Manifest.request.yaml
new file mode 100644
index 0000000..763b0a5
--- /dev/null
+++ b/postman/collections/Fleetbase API/Manifests/Optimize a Manifest.request.yaml	
@@ -0,0 +1,28 @@
+$kind: http-request
+name: "Optimize a Manifest"
+description: |-
+  Re-sequences the stops a driver has not done yet, nearest first.
+
+  This is the driver's optimise, not the orchestrator's. The orchestrator allocates orders across a fleet and produces manifests; this reorders the stops of one manifest that is already assigned.
+
+  It is a nearest-neighbour walk over road distances: from the driver's position to the closest remaining stop, then the closest from there. That is usually a large improvement on an arbitrary order and is not guaranteed optimal.
+
+  Completed and skipped stops keep their place — a route already driven is not re-planned. A manifest with fewer than three stops still to do is returned unchanged, since there is no ordering to find.
+
+  Send `latitude` and `longitude` to start the walk from where the driver actually is. Without them it starts from the first stop still to do.
+url: "{{base_url}}/{{namespace}}/manifests/:id/optimize"
+method: POST
+pathVariables:
+  - key: id
+    value: "{{manifest_id}}"
+    description: (Required) The manifest to re-sequence.
+
+body:
+  type: json
+  content: |-
+    {
+      "latitude": 1.3521,
+      "longitude": 103.8198
+    }
+
+order: 2000
diff --git a/postman/collections/Fleetbase API/Manifests/Retrieve a Manifest.request.yaml b/postman/collections/Fleetbase API/Manifests/Retrieve a Manifest.request.yaml
new file mode 100644
index 0000000..385a240
--- /dev/null
+++ b/postman/collections/Fleetbase API/Manifests/Retrieve a Manifest.request.yaml	
@@ -0,0 +1,14 @@
+$kind: http-request
+name: "Retrieve a Manifest"
+description: |-
+  Retrieves a manifest with its stops, in the sequence they are to be driven.
+
+  Each stop carries its place inline — a route of twenty stops is one request, not twenty-one — along with its status, estimated and actual arrival, and the distance and duration from the previous stop.
+url: "{{base_url}}/{{namespace}}/manifests/:id"
+method: GET
+pathVariables:
+  - key: id
+    value: "{{manifest_id}}"
+    description: (Required) The manifest to retrieve.
+
+order: 1000
diff --git a/postman/collections/Fleetbase API/Manifests/Update a Manifest Stop.params.yaml b/postman/collections/Fleetbase API/Manifests/Update a Manifest Stop.params.yaml
new file mode 100644
index 0000000..d5775bd
--- /dev/null
+++ b/postman/collections/Fleetbase API/Manifests/Update a Manifest Stop.params.yaml	
@@ -0,0 +1,10 @@
+$kind: params
+fields:
+  - name: status
+    type: string
+    required: false
+    description: One of `arrived`, `completed` or `skipped`. Anything else is refused.
+  - name: meta
+    type: object
+    required: false
+    description: Arbitrary metadata to store against the stop, such as a note left on arrival.
diff --git a/postman/collections/Fleetbase API/Manifests/Update a Manifest Stop.request.yaml b/postman/collections/Fleetbase API/Manifests/Update a Manifest Stop.request.yaml
new file mode 100644
index 0000000..c126ce7
--- /dev/null
+++ b/postman/collections/Fleetbase API/Manifests/Update a Manifest Stop.request.yaml	
@@ -0,0 +1,23 @@
+$kind: http-request
+name: "Update a Manifest Stop"
+description: |-
+  Marks a stop on a manifest as arrived, completed or skipped.
+
+  Status changes run through the manifest's own transitions rather than writing a column, so arrival and completion timestamps are recorded and a manifest completes itself when its last stop does.
+
+  Any other status is refused and changes nothing.
+url: "{{base_url}}/{{namespace}}/manifest-stops/:id"
+method: PATCH
+pathVariables:
+  - key: id
+    value: "{{manifest_stop_id}}"
+    description: (Required) The stop to update.
+
+body:
+  type: json
+  content: |-
+    {
+      "status": "arrived"
+    }
+
+order: 3000

From e7933b8e9854a52ef2db557ab2823d8d74402579 Mon Sep 17 00:00:00 2001
From: "Ronald A. Richardson" <me@ron.dev>
Date: Mon, 31 Aug 2026 12:06:07 +0800
Subject: [PATCH 2/2] fix: make the new driver and manifest requests survive a
 contract run

The collection asserts every request returns 2xx, so a request that
cannot succeed unattended reads as a broken endpoint.

- Create a Driver seeds a known password and captures the generated
  email and phone. They are generated inline, so the response is the
  only place to read them back, and without them the password requests
  had no identity and no current password to prove.
- The password and manifest requests run before Delete a Driver rather
  than after it. At 13000 they addressed a driver deleted at 5000.
- Reset Driver Password skips itself: its code arrives by email or SMS,
  which an automated run cannot read.
- Request Driver Password Reset addresses a reserved address that
  belongs to nobody. The endpoint answers identically for an unknown
  identity, so it is still exercised and no stranger is sent a code.
- The manifest requests skip themselves when the run found no manifest.
---
 .../Fleetbase API/.resources/definition.yaml   | 14 ++++++++++++++
 .../Change Driver Password.request.yaml        | 14 ++++++++++++--
 .../Drivers/Create a Driver.request.yaml       | 16 +++++++++++++++-
 .../Drivers/List Driver Manifests.request.yaml | 18 +++++++++++++++++-
 .../Request Driver Password Reset.request.yaml |  6 ++++--
 .../Drivers/Reset Driver Password.request.yaml | 17 ++++++++++++++++-
 .../Manifests/Optimize a Manifest.request.yaml | 16 ++++++++++++++++
 .../Manifests/Retrieve a Manifest.request.yaml | 16 ++++++++++++++++
 .../Update a Manifest Stop.request.yaml        | 16 ++++++++++++++++
 9 files changed, 126 insertions(+), 7 deletions(-)

diff --git a/postman/collections/Fleetbase API/.resources/definition.yaml b/postman/collections/Fleetbase API/.resources/definition.yaml
index 4d7e587..4c399b3 100644
--- a/postman/collections/Fleetbase API/.resources/definition.yaml	
+++ b/postman/collections/Fleetbase API/.resources/definition.yaml	
@@ -40,6 +40,20 @@ variables:
   customer_phone: ""
   verification_code: ""
   push_token: ""
+  driver_identity: ""
+  driver_email: ""
+  driver_phone: ""
+  # Seeded on Create a Driver so the password endpoints have a known starting
+  # point; `driver_password` then tracks whatever is currently in force.
+  driver_seed_password: "contract-seed-password"
+  driver_password: ""
+  driver_new_password: "contract-changed-password"
+  # A reserved address (RFC 2606) that can never be delivered to. Requesting a
+  # reset answers the same way for an unknown identity as for a real one, so the
+  # endpoint is still exercised and no stranger receives a reset code.
+  driver_reset_identity: "driver-password-reset@example.com"
+  manifest_id: ""
+  manifest_stop_id: ""
 scripts:
   - type: http:afterResponse
     code: |
diff --git a/postman/collections/Fleetbase API/Drivers/Change Driver Password.request.yaml b/postman/collections/Fleetbase API/Drivers/Change Driver Password.request.yaml
index 2414aa6..054e432 100644
--- a/postman/collections/Fleetbase API/Drivers/Change Driver Password.request.yaml	
+++ b/postman/collections/Fleetbase API/Drivers/Change Driver Password.request.yaml	
@@ -17,10 +17,20 @@ body:
   type: json
   content: |-
     {
-      "current_password": "{{driver_current_password}}",
+      "current_password": "{{driver_password}}",
       "password": "{{driver_new_password}}",
       "password_confirmation": "{{driver_new_password}}",
       "device_name": "navigator"
     }
 
-order: 13000
+scripts:
+  - type: afterResponse
+    code: |-
+      // The password in force has changed, so anything authenticating later
+      // must use the new one.
+      if (pm.response.code === 200) {
+          pm.environment.set("driver_password", pm.variables.get("driver_new_password"));
+      }
+    language: text/javascript
+
+order: 4200
diff --git a/postman/collections/Fleetbase API/Drivers/Create a Driver.request.yaml b/postman/collections/Fleetbase API/Drivers/Create a Driver.request.yaml
index d4ce836..08e6c1b 100644
--- a/postman/collections/Fleetbase API/Drivers/Create a Driver.request.yaml	
+++ b/postman/collections/Fleetbase API/Drivers/Create a Driver.request.yaml	
@@ -11,7 +11,8 @@ body:
     {
       "name": "John Doe",
       "email": "{{$randomEmail}}",
-      "phone": "{{$randomPhoneNumber}}"
+      "phone": "{{$randomPhoneNumber}}",
+      "password": "{{driver_seed_password}}"
     }
 scripts:
   - type: afterResponse
@@ -21,6 +22,19 @@ scripts:
 
       cv.set("driver_id", json_response.id);
       cv.set("driver_name", json_response.name);
+
+      // The email and phone are generated inline, so the response is the only
+      // place they can be read back. Without them the password and login
+      // requests below have no identity to use.
+      cv.set("driver_email", json_response.email);
+      cv.set("driver_phone", json_response.phone);
+      cv.set("driver_identity", json_response.email);
+
+      // Tracks the password currently in force, so Change Driver Password can
+      // prove the old one and later requests still know what it is.
+      // pm.variables resolves across scopes; the seed is a collection variable,
+      // which pm.environment cannot see.
+      cv.set("driver_password", pm.variables.get("driver_seed_password"));
     language: text/javascript
 examples: ./.resources/Create a Driver.resources/examples
 order: 1000
diff --git a/postman/collections/Fleetbase API/Drivers/List Driver Manifests.request.yaml b/postman/collections/Fleetbase API/Drivers/List Driver Manifests.request.yaml
index 4712fdf..5a88ea9 100644
--- a/postman/collections/Fleetbase API/Drivers/List Driver Manifests.request.yaml	
+++ b/postman/collections/Fleetbase API/Drivers/List Driver Manifests.request.yaml	
@@ -13,4 +13,20 @@ pathVariables:
     value: "{{driver_id}}"
     description: (Required) The driver whose manifests to list.
 
-order: 13300
+scripts:
+  - type: afterResponse
+    code: |-
+      // Captures a manifest for the Manifests folder to address. On an instance
+      // with no routes assigned this simply finds nothing, and those requests
+      // skip themselves.
+      if (pm.response.code === 200) {
+          const body = pm.response.json();
+          const rows = Array.isArray(body) ? body : (body.data || []);
+
+          if (rows.length) {
+              pm.environment.set("manifest_id", rows[0].id);
+          }
+      }
+    language: text/javascript
+
+order: 4500
diff --git a/postman/collections/Fleetbase API/Drivers/Request Driver Password Reset.request.yaml b/postman/collections/Fleetbase API/Drivers/Request Driver Password Reset.request.yaml
index 824808a..803dae8 100644
--- a/postman/collections/Fleetbase API/Drivers/Request Driver Password Reset.request.yaml	
+++ b/postman/collections/Fleetbase API/Drivers/Request Driver Password Reset.request.yaml	
@@ -6,6 +6,8 @@ description: |-
   The code goes by email or SMS depending on whether `identity` looks like an email address or a phone number.
 
   The response is the same whether or not the identity belongs to a driver. That is deliberate: an endpoint that answered differently for an unknown number would be a way to enumerate an organization's drivers.
+
+  `driver_reset_identity` defaults to a reserved address that belongs to nobody, so running the collection documents the endpoint without sending mail to a stranger. Point it at a real driver to exercise delivery.
 url: "{{base_url}}/{{namespace}}/drivers/forgot-password"
 method: POST
 
@@ -13,7 +15,7 @@ body:
   type: json
   content: |-
     {
-      "identity": "{{driver_email}}"
+      "identity": "{{driver_reset_identity}}"
     }
 
-order: 13100
+order: 4300
diff --git a/postman/collections/Fleetbase API/Drivers/Reset Driver Password.request.yaml b/postman/collections/Fleetbase API/Drivers/Reset Driver Password.request.yaml
index 90262f6..538b435 100644
--- a/postman/collections/Fleetbase API/Drivers/Reset Driver Password.request.yaml	
+++ b/postman/collections/Fleetbase API/Drivers/Reset Driver Password.request.yaml	
@@ -18,4 +18,19 @@ body:
       "password": "{{driver_new_password}}"
     }
 
-order: 13200
+scripts:
+  - type: beforeRequest
+    code: |-
+      // The reset code is delivered by email or SMS, so an automated run has no
+      // way to read it. Skipped rather than failed: the request is here to be
+      // documented and to work for anyone who sets `verification_code`, and a
+      // request that cannot succeed should not be reported as a broken endpoint.
+      const code = pm.environment.get("verification_code");
+      const unresolved = !code || /^\{\{.*\}\}$/.test(String(code));
+
+      if (unresolved && typeof pm.execution !== "undefined" && pm.execution.skipRequest) {
+          pm.execution.skipRequest();
+      }
+    language: text/javascript
+
+order: 4400
diff --git a/postman/collections/Fleetbase API/Manifests/Optimize a Manifest.request.yaml b/postman/collections/Fleetbase API/Manifests/Optimize a Manifest.request.yaml
index 763b0a5..9dd1686 100644
--- a/postman/collections/Fleetbase API/Manifests/Optimize a Manifest.request.yaml	
+++ b/postman/collections/Fleetbase API/Manifests/Optimize a Manifest.request.yaml	
@@ -25,4 +25,20 @@ body:
       "longitude": 103.8198
     }
 
+scripts:
+  - type: beforeRequest
+    code: |-
+      // Manifests are produced by dispatch — the consumable API deliberately
+      // cannot create one — so a fresh instance has none to address. Skipped
+      // rather than failed: the request documents the endpoint and runs for
+      // anyone whose instance has a manifest, and a missing fixture is not an
+      // endpoint fault.
+      const id = pm.environment.get("manifest_id");
+      const unresolved = !id || /^\{\{.*\}\}$/.test(String(id));
+
+      if (unresolved && typeof pm.execution !== "undefined" && pm.execution.skipRequest) {
+          pm.execution.skipRequest();
+      }
+    language: text/javascript
+
 order: 2000
diff --git a/postman/collections/Fleetbase API/Manifests/Retrieve a Manifest.request.yaml b/postman/collections/Fleetbase API/Manifests/Retrieve a Manifest.request.yaml
index 385a240..1511d53 100644
--- a/postman/collections/Fleetbase API/Manifests/Retrieve a Manifest.request.yaml	
+++ b/postman/collections/Fleetbase API/Manifests/Retrieve a Manifest.request.yaml	
@@ -11,4 +11,20 @@ pathVariables:
     value: "{{manifest_id}}"
     description: (Required) The manifest to retrieve.
 
+scripts:
+  - type: beforeRequest
+    code: |-
+      // Manifests are produced by dispatch — the consumable API deliberately
+      // cannot create one — so a fresh instance has none to address. Skipped
+      // rather than failed: the request documents the endpoint and runs for
+      // anyone whose instance has a manifest, and a missing fixture is not an
+      // endpoint fault.
+      const id = pm.environment.get("manifest_id");
+      const unresolved = !id || /^\{\{.*\}\}$/.test(String(id));
+
+      if (unresolved && typeof pm.execution !== "undefined" && pm.execution.skipRequest) {
+          pm.execution.skipRequest();
+      }
+    language: text/javascript
+
 order: 1000
diff --git a/postman/collections/Fleetbase API/Manifests/Update a Manifest Stop.request.yaml b/postman/collections/Fleetbase API/Manifests/Update a Manifest Stop.request.yaml
index c126ce7..f8e20c4 100644
--- a/postman/collections/Fleetbase API/Manifests/Update a Manifest Stop.request.yaml	
+++ b/postman/collections/Fleetbase API/Manifests/Update a Manifest Stop.request.yaml	
@@ -20,4 +20,20 @@ body:
       "status": "arrived"
     }
 
+scripts:
+  - type: beforeRequest
+    code: |-
+      // Manifests are produced by dispatch — the consumable API deliberately
+      // cannot create one — so a fresh instance has none to address. Skipped
+      // rather than failed: the request documents the endpoint and runs for
+      // anyone whose instance has a manifest, and a missing fixture is not an
+      // endpoint fault.
+      const id = pm.environment.get("manifest_stop_id");
+      const unresolved = !id || /^\{\{.*\}\}$/.test(String(id));
+
+      if (unresolved && typeof pm.execution !== "undefined" && pm.execution.skipRequest) {
+          pm.execution.skipRequest();
+      }
+    language: text/javascript
+
 order: 3000