← Back to integrations education
API order ingestion
How to send delivery orders to Porterchain via API: authentication, payload, and what we support. Practical overview for technical teams.
When you’re ready to push orders from your system to ours, we offer an API for creating stops and runs. You authenticate, send your payload with address and contact data, and we confirm and plan the route. This page gives a practical overview of what’s involved — we don’t overpromise; we outline what we support so you can plan your integration.
What the API does
The API lets you create delivery stops and runs programmatically. You send the same data you’d put in a CSV: delivery address, contact, time window, reference. We validate, geocode where needed, and add the stops to a run. You get a response with identifiers so you can track status in your dashboard or via webhooks if we support them for your account. We’ll provide documentation and a clear schema so your team can integrate without surprises.
Authentication and environment
You’ll get credentials (e.g. API key) and use them to authenticate requests. We may offer a sandbox or test environment so you can validate payloads before going live. Going live means switching to production credentials and following our rate limits and conventions. We’ll confirm what’s available for your account during onboarding.
What we don’t promise
We don’t claim to support every possible integration pattern or legacy format. Our API is designed for delivery order ingestion — structured address and contact data, time windows, references. If you have unusual requirements (e.g. custom fields, complex multi-leg logic), we’ll discuss feasibility during onboarding rather than overpromising. The goal is a reliable, maintainable integration that fits how we run delivery.