Partner API
REST with idempotency keys and granular permissions. Docs ship inside the customer environment — not on this website.
Integrations
Partner API, SFTP file intake, AS2, webhooks and an outbound message outbox. Pathfinder is built to be operated — not a folder of CSV drops and a hope that Jitterbit stays up.
Intake today
64
Outbox queued
3
Failed 24h
1
| Channel | Message | Status |
|---|---|---|
| SFTP intake | ASN-8821.xml | Processed |
| Partner API | POST /orders | Accepted |
| AS2 | EDI 856 · SSCC | Delivered |
| Outbox | shipment.closed | Retry 2/5 |
Mappings, file intake, outbound delivery, API keys and activity sit in administration. The aim is Jitterbit-class capability that a competent ops-IT pair can operate without a six-month integration programme for every new client.
API reference, Postman and Insomnia exports are available inside the customer’s Pathfinder environment. This marketing site does not publish a public API console or a login to those docs.
Systems we connect
Pathfinder does not publish a wall of vendor logos we have not certified. We connect the hosts you already run via API, files and AS2.
REST with idempotency keys and granular permissions. Docs ship inside the customer environment — not on this website.
Stable-file intake, blob retention, run timelines, and outbound file delivery the warehouse can diagnose.
Trading-partner AS2 for EDI-style interchange, including outbound 856-class messages where the operation requires them.
A governed outbound message outbox with delivery, retry and activity — not a fire-and-forget script.
OIDC SSO for Microsoft Entra ID, Okta, or a generic issuer. Pathfinder support sign-in can require TOTP MFA.
Connect the systems you already run through the API and files. We do not sell a catalogue of paid point connectors.
Tell us about the warehouse. We arrange a demonstration on a Pathfinder instance — not a public login from this website.