Build delivery integrations for marketplaces, partners, and external systems using a consistent API model.
Seeplus is a delivery orchestration platform that enables external systems, such as marketplaces and partner platforms, to integrate with multiple courier providers through a consistent set of APIs.
Instead of integrating separately with each courier, partners integrate once with Seeplus and use the same APIs, structure, and workflows to manage delivery operations across multiple providers.
This approach reduces integration complexity, accelerates time to market, and ensures a consistent delivery experience across different courier networks.
Easy Page Navigation
1. Overview
What is Seeplus?
Seeplus is a delivery orchestration platform that enables external systems, such as marketplaces and partner platforms, to integrate with multiple courier providers through a consistent set of APIs.
Integration flow
-
Set up your operational structure using the Setup API.
-
Retrieve available delivery methods and quotes using the Delivery Methods API.
-
Create delivery orders using the New Order API.
-
Receive real-time delivery updates via webhooks.
-
Manage the delivery lifecycle using the relevant operational APIs, such as Ready for Pickup, Cancel Delivery, and Retry Delivery.
Who this section is for
-
Marketplaces
-
External ordering systems
-
Technical partners and developers responsible for delivery integrations
2. Getting Started
Sandbox & Testing Environment
To start developing your integration with Seeplus, request access to the Sandbox & Testing Environment.
This allows you to begin testing the APIs and validating your implementation in a non-production environment.
Recommended sequence:
-
Request access to the Sandbox & Testing Environment
-
Develop and test the integration flow
-
Book a meeting with the Seeplus team to validate the integration flow
-
Obtain the production API token required to start using the Setup API in production
Important
Once development is complete, you must book a meeting with the Seeplus team to validate the integration flow and obtain the production API token required to start using the Setup API in production.
3. Developer Onboarding
Step 1: Authentication and access
The Setup API requires an API token, which must be requested from the Seeplus team.
Subsequent API requests require:
-
Origin ID
-
Location ID
These identifiers are returned when each location is created and must be used in subsequent API calls.
Step 2 — Account setup
Before requesting delivery options or creating orders, your operational structure must be created [Setup API].
Origins
The origin is the delivery configuration layer. It contains:
-
Delivery method settings
-
Courier settings
Locations
The location is the physical pickup location. It includes:
-
Name
-
Address
-
Contact details
-
Pickup details
-
Delivery schedule, such as 24/7 availability or specific date and time slots
Best practice: to maximise flexibility, we recommend creating one origin per location and managing delivery configuration at origin level.
Outcome of this step
-
Request delivery quotes
-
Create delivery orders
4. Delivery Flow
Main Integration Flow
The main integration flow covers the steps required to retrieve delivery options, create an order, and receive delivery updates. Additional operational actions, such as WhenReady, cancellation, and retry, are only used in specific scenarios.
Main flow:
-
Retrieve delivery methods and quotes
-
Create a delivery order
-
Configure webhooks and share your endpoint URL with the Seeplus team
Retrieve delivery methods and quotes
Use the Delivery Methods API to retrieve:
-
The delivery methods configured for the origin
-
The corresponding delivery quotes
Response behaviour
-
The location configuration, including delivery schedules and serviceability constraints, such as the distance between the pickup and drop-off locations
-
The delivery methods configured for the origin
Delivery quotes are returned when the service is available. Pickup times may vary depending on real-time courier availability.
Important behaviour
-
Only the delivery methods configured for the origin are returned
-
Each delivery method may return multiple quotes
Example
-
Delivery method: ASAP
-
Couriers: Courier A and Courier B
The response may return ASAP → Courier A + price and ASAP → Courier B + price.
Create a delivery order
Use the New Order API to:
-
Submit a delivery request
-
Trigger courier dispatch
-
Receive a tracking URL
Important rules
-
Valid delivery method: the delivery method used to create an order must be one of the delivery methods returned by the Delivery Methods API.
-
Order timing: the New Order API should be called shortly after retrieving quotes. As a best practice, create the order within approximately 15 minutes of requesting delivery quotes.
-
Payment status: orders sent to Seeplus must already have been paid for by the end customer.
-
Customer contact information: a valid customer mobile number must be provided.
Delivery methods
-
ASAP — the courier is requested immediately.
-
WhenReady — the courier is requested only after the order has been prepared and marked as ready.
-
Scheduled — the courier is requested according to the selected delivery time window.
Best practice: it is not recommended to configure ASAP and WhenReady simultaneously for the same origin, as both represent the same customer-facing delivery option.
Webhooks configuration
Webhooks provide real-time delivery status updates and are part of the main integration flow.
Seeplus sends HTTP requests to your endpoint whenever an order status changes.
What you need to do
-
Provide your webhook URL to the Seeplus team
-
Ensure your endpoint accepts application/json
-
Ensure your endpoint returns HTTP 200
Typical events
-
Order Ready
-
Order Delivered
-
Order Cancelled
-
Order Returned
Configuration
-
Which events you want to receive
-
The level of payload detail
Important: to enable webhook notifications, you must share your endpoint URL with the Seeplus team.
Optional flow - WhenReady
This flow only applies if the selected delivery method is WhenReady. It does not apply to ASAP or Scheduled deliveries.
-
The order is created, but no courier is requested yet
-
The order is prepared
-
The external system calls the Ready for Pickup API. As an alternative, you can use the Seeplus app to confirm that the order is ready.
-
Seeplus requests the courier
[Ready for Pickup API]
Secondary flow - Cancel delivery
This is not part of the main flow. Use the Cancel Delivery API only if you need to cancel a delivery.
Use the Cancel Delivery API or the Seeplus app to cancel a delivery. Cancellation is only allowed before a courier picks up the order.
[Cancel Delivery API]
Secondary flow - Retry delivery
This is not part of the main flow. Use the Retry Delivery API only if you need to request a new delivery after a cancellation.
Retry delivery depends on a previous cancellation, so it should only be used after the Cancel Delivery flow.
Use the Retry Delivery API to request a new delivery after a previous delivery has been cancelled. This triggers a new courier request.
[Retry Delivery API]
5. Concepts and Configurations
Key Entities
Origin
The origin is the delivery configuration layer. This is where delivery methods and courier settings are configured.
A single origin can be associated with more than one location. However, the recommended setup is to create one origin for each location.
This is recommended because delivery methods and courier settings are managed at origin level. By using one origin per location, you gain more operational flexibility and can configure each location independently.
-
Delivery methods
-
Courier settings
Recommended setup: use one origin per location to allow configuration flexibility on a location-by-location basis.
Location
The location is the physical pickup location associated with an origin.
This is where you define the operational details required for delivery execution and courier communication.
A location should include:
-
Address of the location
-
Contact details for the location, so the courier can make contact if any issue arises during pickup
-
Scheduling information, so Seeplus knows when the store can receive orders and can communicate that availability to couriers
If the external system is responsible for managing location opening hours, we recommend configuring the location schedule as 24 hours a day, 7 days a week.
Uber Direct configurations
Delivery methods
-
ASAP — the courier is requested immediately
-
WhenReady — the courier is requested only after the order has been prepared and marked as ready
-
Scheduled — the courier is requested according to the selected delivery time window
Location configuration
-
Schedules — delivery schedule, such as 24/7 availability or specific date and time slots
-
Pickup details — instructions for the courier about the pickup location
Courier settings
Courier settings define how deliveries are completed and how delivery exceptions are handled. These settings are configured at origin level and apply to all delivery requests associated with that origin.
Proof of Delivery (POD)
PIN — if enabled, the courier must request a PIN code from the customer to complete the delivery.
Photo check — if enabled, the courier must take a photo at the time of delivery as proof.
Best practice: using a PIN is recommended for higher-risk deliveries, as it provides stronger confirmation that the order was delivered to the correct customer.
Undeliverable actions
Undeliverable actions define what happens if the courier is unable to complete the delivery.
-
Customer not available
-
Incorrect address
-
No response from the customer
Available options may include:
-
Leave at door (undeliverable_action_leave_at_door)
-
Return to store (undeliverable_action_return)
-
Discard (undeliverable_action_discard)
Jet Go configurations
Under construction: Jet Go configuration details will be added in a future update.
6. APIs
Setup API
Create origins, locations, and delivery configuration.
View technical documentation
Order APIs
Includes Delivery Methods and New Order. Retrieve delivery options and quotes, then create delivery requests.
View technical documentation
Ready for Pickup API
Trigger courier dispatch for WhenReady orders.
View technical documentation
Cancel Delivery API
Cancel delivery requests.
View technical documentation
Retry Delivery API
Request a new delivery after a previous delivery has been cancelled.
View technical documentation
7. Sandbox & Testing Environment
Request sandbox access
Complete the form below to receive access details.
What happens next
-
Credentials
-
Sandbox access
-
Test data will be prepared so you can start validating the APIs
We aim to respond quickly and help you get started as soon as possible
Recommended use cases
-
Validate authentication and access
-
Test your operational setup
-
Retrieve delivery methods and quotes
-
Create test orders
-
Validate webhook handling before moving to production
8. Production Readiness & Integration Validation
Validation session
Upon completion of development and testing, partners are required to schedule a validation session with the Seeplus team to assess integration readiness for production.
This session will include:
-
End-to-end validation of the integration flow
-
Review of key operational scenarios
-
Formal confirmation of production readiness
Following successful validation, the production API token will be issued, enabling access to the Setup API in the live environment.