Direct API lane

Atlas DataSynch Non-GCP Integration Guide

Use Atlas DataSynch directly from partner systems, scripts, webhooks, or internal services.

Partner app

Use x-api-key and send records directly to intake, import, telemetry, geofence, or dispatch routes.

Webhook sender

Use /api/datasynch/integrations/receiver for semi-normalized payloads that need processing.

Internal script

Use quick-start examples as known-good request bodies for repeatable imports and smoke tests.

Direct lane checklist
txt
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.
Webhook-style intake request
http
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"
      }
    }
  ]
}
Keep exploring

Explore related solutions and API pages

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.

Back to map