Overview
This page provides detailed descriptions for all fields in the delivery object returned by the API.Core Identifiers
string (UUID)
required
Unique identifier for the delivery
- Used for API calls and internal references
- Automatically generated on creation
- Example:
"abc123-def456-ghi789"
string
required
Human-readable tracking identifier
- Shared with customers for tracking
- 12-character alphanumeric string
- Example:
"CHI-ABC123"
string (UUID)
required
ID of the user who created the delivery
- Links to the API key owner
- Used for authorization checks
string (UUID)
ID of the assigned driver
nullif no driver assigned yet- Populated when driver accepts the delivery
Status & Type
enum
required
Current status of the deliveryPossible values:
PENDING- Created, awaiting payment or driver assignmentSTARTED- Driver has accepted and started the deliveryPICKED-UP- Package picked up by driverCOMPLETED- Successfully deliveredCANCELLED- Delivery was cancelled
enum
required
Type of delivery servicePossible values:
SendDelivery- Standard delivery from point A to BRequestPickup- Pickup request service
string
Optional custom name for the delivery
- Helps identify deliveries in your system
- Example:
"Office Supplies","Customer Order #1234"
Location & Route
string
required
Full address of the pickup location
- Human-readable format
- Example:
"123 Main Street, Victoria Island, Lagos"
object
required
Precise coordinates of the pickup location
string
required
Full address of the delivery destination
- Human-readable format
- Example:
"456 Business Avenue, Lekki, Lagos"
object
required
Precise coordinates of the destination
object
Driver’s current location during delivery
- Only available when delivery is in progress
nullwhen delivery is pending or completed- Updates in real-time via WebSocket
object
Calculated route information from pickup to destination
Contact Information
string
required
Recipient’s phone number
- Normalized to Nigerian format (234 prefix)
- Example:
"2348012345678"
string
required
Sender’s phone number
- Normalized to Nigerian format (234 prefix)
- Example:
"2348087654321"
string
Special delivery instructions
- Visible to the assigned driver
- Example:
"Please call before delivery","Leave at gate"
Payment & Pricing
number
required
Total delivery cost in Naira (₦)
- Includes all fees and charges
- Example:
2500(₦2,500)
boolean
required
Payment status
trueif payment has been completedfalseif payment is pending
string
Payment transaction reference
- Links to the payment record
- Populated after successful payment
Package Information
array
Photos of the package
- Array of image objects
- Uploaded by driver or sender
- Used for proof of delivery
Timing & Schedule
datetime
Scheduled delivery time
- ISO 8601 format
nullfor immediate deliveries- Example:
"2025-01-15T14:00:00.000Z"
datetime
When the driver picked up the package
- ISO 8601 format
nulluntil package is picked up- Example:
"2025-01-15T10:30:00.000Z"
datetime
When the driver arrived at the pickup location
- ISO 8601 format
nulluntil driver arrives- Example:
"2025-01-15T10:15:00.000Z"
datetime
When the driver arrived at the destination
- ISO 8601 format
nulluntil driver arrives at destination- Example:
"2025-01-15T11:00:00.000Z"
datetime
required
When the delivery was created
- ISO 8601 format
- Automatically set on creation
- Example:
"2025-01-15T10:00:00.000Z"
datetime
required
Last modification timestamp
- ISO 8601 format
- Updates automatically on any change
- Example:
"2025-01-15T10:45:00.000Z"
Driver Status
boolean
required
Whether the driver has arrived at the destination
- Used for arrival notifications
truewhen driver reaches destination
Bulk Deliveries
string (UUID)
Bulk delivery group identifier
nullfor single deliveries- All deliveries with the same bulk ID are part of one bulk order
- Used to group multiple deliveries from the same pickup location
number
Position in bulk delivery sequence
nullfor single deliveries- Determines the order for multi-stop routes
- Example:
1,2,3for first, second, third stops
string
Order code for the delivery
- Optional reference code for tracking
- Can be used to link delivery to external order systems
nullif not provided
Field Exclusions
The following fields exist in the database but are excluded from API responses for security and business logic reasons:usesPromo- Internal promo trackingpromoPercentage- Internal pricing calculationdriverCut- Internal revenue splitcompanyCut- Internal revenue splitshop- Internal shop referencevehicleDirection- Internal trackinginActive- Internal flagdeliveryDate- Deprecated (usecreatedAtorscheduledTime)deliveryTime- Deprecated (use timestamp fields)pickupTime- Deprecated (usepickedUpAt)
