Guided first
Start with workflow intent, then expose route details. Users should not have to reverse-engineer the route order from Swagger.
Guided API documentation, quick starts, examples, and a developer workbench for Atlas DataSynch.
Use this center to move from business workflows into route families, schemas, request bodies, examples, GCP paths, and direct API calls.
Search the Swagger-compliant OpenAPI contract and inspect schemas, parameters, and routes.
Use workflow presets for common DataSynch jobs and copy request examples.
Start with practical workflows such as importing locations, sending telemetry, or dispatching a webhook.
Use DataSynch through Google API Gateway, Application Integration, and Integration Connectors.
Use DataSynch directly from partner apps, webhooks, scripts, queues, carrier feeds, or internal services.
Copy known-good request bodies, curl commands, and JavaScript fetch snippets.
Start with workflow intent, then expose route details. Users should not have to reverse-engineer the route order from Swagger.
Swagger remains the source of contract truth, but the wrapper explains when and why each route matters.
Every important route should explain what appears in the app afterward and which DataSynch surface owns the object.
Users must be able to find endpoints by business job, schema, object type, tag, and route.
Developer documentation should help readers move back to the business context as easily as they move into routes, examples, and schemas.
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.