Partner app
Use x-api-key and send records directly to intake, import, telemetry, geofence, or dispatch routes.
Use Atlas DataSynch directly from partner systems, scripts, webhooks, or internal services.
Use x-api-key and send records directly to intake, import, telemetry, geofence, or dispatch routes.
Use /api/datasynch/integrations/receiver for semi-normalized payloads that need processing.
Use quick-start examples as known-good request bodies for repeatable imports and smoke tests.
1. Get a DataSynch API key or use app tenant authentication.
2. Select the tenant/company, workspace, and manifest context.
3. Choose a route by job: import records, send telemetry, create geofence, evaluate XREF, dispatch action.
4. Send records with stable external IDs and source metadata.
5. Read runs, exceptions, dispatch logs, and app surfaces to verify results.
6. Promote repeatable setups into integration profiles.POST /api/datasynch/integrations/receiver
content-type: application/json
x-api-key: $ATLAS_DATASYNCH_API_KEY
{
"manifestId": "manifest_demo_001",
"sourceKind": "webhook",
"connectorId": "partner-webhook",
"connectionName": "Partner webhook feed",
"records": [
{
"externalId": "partner-event-001",
"recordType": "shipment_status",
"fields": {
"shipmentId": "SHIP-100045",
"eventCode": "ARRIVED",
"eventTime": "2026-06-24T17:30:00.000Z"
}
}
]
}Direct API readers should be able to move into DataSynch, API integration, EDI/cXML, XREF, scanner, and geofencing pages without searching for the next page manually.
Guided docs, API Explorer, Workbench, quick starts, examples, GCP, and non-GCP integration notes.
Find routes by job, tag, schema, endpoint, or app surface.
Run guided workflows for imports, XREF, geofences, telemetry, dispatch, and run logs.
Copy known-good request bodies for DataSynch API testing and partner integration.
Map-aware operating hub for locations, partner data, Xref, telemetry, inventory, exceptions, and normalized workflow records.
Create radius or polygon boundaries that turn movement, scans, arrivals, exits, and dwell time into operational events.
Connect accounts, contacts, partners, campaigns, field coverage, support activity, and customer sites to operational context.
Track products, parts, consignment stock, truck inventory, store inventory, and high-value items by location or movement.
Use Android/mobile scanning for pick-pack, scan-n-pack, proof capture, proximity checks, and field-event workflows.
Convert partner, customer, ERP, EDI, spreadsheet, or app-specific codes into usable internal values.
Route alerts, webhooks, exceptions, and downstream actions when operational events need a response.
RESTful access for GCP, webhooks, EDI, EDIFACT, cXML, spreadsheets, apps, and partner workflows.
Consume or issue structured business documents and connect them to map-aware workflows.
Build route visuals for field movement, customer visits, trips, vessels, aircraft, and operational planning.
Quick starts, field guides, help files, API explainers, and implementation notes for business and technical users.