Use the solution pages for plain-language value
The solution pages explain what a company can achieve before asking a technical reader to inspect route contracts or schemas.
Atlasemoji implementation
Implementation notes
This page connects the plain-language solution pages to the DataSynch Developer Center without exposing private implementation details.
The right structure is simple: explain the business use case, show related solution pages, then link to the API Explorer, Workbench, examples, GCP guide, and non-GCP guide where the build path belongs.
Solution map
Explore the solution set
Use the Developer Center for build paths
The DataSynch Developer Center explains how to connect those solution stories to route families, examples, and workbench presets.
Keep private implementation details out of marketing
Public docs should explain the model without exposing credentials, private tenant rules, internal controls, or production-only assumptions.
Move gradually from story to API
Every solution should have a buyer-readable path and a technical path without turning the marketing page into a Swagger dump.
Technical proof path
API documentation and implementation routes
Use these pages to move from a solution story into contract review, guided tests, deployment choices, and request examples.
Start here
DataSynch Developer Center
Guided docs, API Explorer, Workbench, quick starts, examples, GCP, and non-GCP integration notes.
Swagger
Searchable API Explorer
Find routes by job, tag, schema, endpoint, or app surface.
Build
Developer Workbench
Run guided workflows for imports, XREF, geofences, telemetry, dispatch, and run logs.
Examples
API Examples
Copy known-good request bodies for DataSynch API testing and partner integration.