← Back to Developer CenterFind GCP routes
Google Cloud lane

Atlas DataSynch GCP Integration Guide

Use Atlas DataSynch with Google API Gateway and GCP Application Integration.

Recommended GCP route order

  1. Call /api/datasynch/health.
  2. Call /api/datasynch/application-integration/status.
  3. Use profiles for reusable source, processing, and outbound configuration.
  4. Send records to the integration receiver or a domain import route.
  5. Read runs, exceptions, and dispatch logs after execution.

GCP-safe design rules

  • Never expose secrets in readiness responses.
  • Keep tenant, workspace, manifest, profile, connector, and run IDs traceable.
  • Use stable operation IDs from the OpenAPI contract.
  • Prefer queued, traceable writes over silent one-off side effects.
Gateway checklist
txt
1. Confirm /api/datasynch/health responds.
2. Confirm /api/datasynch/application-integration/status returns safe readiness flags.
3. Deploy docs/openapi/datasynch-gateway-v1.yaml to Google API Gateway.
4. Configure x-api-key or gateway auth as required.
5. Create or select tenant/company, workspace, and manifest context.
6. Create or select an integration profile.
7. Send records to /api/datasynch/integrations/receiver or a domain import route.
8. Review runs, exceptions, and dispatch logs in the DataSynch app.
Sample readiness call
bash
curl -X GET "https://atlasemoji--epicatlas-4361e.us-east4.hosted.app/api/datasynch/application-integration/status" \
  -H "x-api-key: $ATLAS_DATASYNCH_API_KEY"
Keep exploring

Explore related solutions and API pages

This GCP guide is one technical path. These links help readers connect it back to DataSynch, integration, EDI/cXML, geofencing, and the other solution pages.

Back to map
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.

Atlas DataSynch

Map-aware operating hub for locations, partner data, Xref, telemetry, inventory, exceptions, and normalized workflow records.

Geofencing

Create radius or polygon boundaries that turn movement, scans, arrivals, exits, and dwell time into operational events.

CRM

Connect accounts, contacts, partners, campaigns, field coverage, support activity, and customer sites to operational context.

Inventory & Items

Track products, parts, consignment stock, truck inventory, store inventory, and high-value items by location or movement.

Handheld Scanner

Use Android/mobile scanning for pick-pack, scan-n-pack, proof capture, proximity checks, and field-event workflows.

Xref / Partner Mapping

Convert partner, customer, ERP, EDI, spreadsheet, or app-specific codes into usable internal values.

Atlas Intercept

Route alerts, webhooks, exceptions, and downstream actions when operational events need a response.

API & Integration Hub

RESTful access for GCP, webhooks, EDI, EDIFACT, cXML, spreadsheets, apps, and partner workflows.

EDI, EDIFACT & cXML

Consume or issue structured business documents and connect them to map-aware workflows.

Travel & Routing

Build route visuals for field movement, customer visits, trips, vessels, aircraft, and operational planning.

Learning & Help

Quick starts, field guides, help files, API explainers, and implementation notes for business and technical users.