GET/api/datasynch/healthHealthGCP safeUI backed
Check DataSynch health
Confirm that the DataSynch API is responding before testing deeper workflows.
- Required context
- none
- App surface
- DataSynch → Developer Center → API Explorer
- Related schema
- HealthResponse
- Next step
- /api/datasynch/application-integration/status
GET/api/datasynch/application-integration/statusHealthGCP safeUI backed
Check GCP Application Integration readiness
Inspect safe configuration status for Application Integration execution.
- Required context
- project configuration
- App surface
- DataSynch → Integrations → Application Integration
- Related schema
- ApplicationIntegrationStatusResponse
- Next step
- /api/datasynch/integrations/profiles
POST/api/datasynch/integrations/receiverIntegration IntakeGCP safeUI backed
Receive integration payload records
Accept normalized or semi-normalized records from GCP Application Integration, a webhook, file processor, scanner, or internal source.
- Required context
- companyId when enforced, workspaceId when available, manifestId, connectorId, sourceKind
- App surface
- DataSynch → Pipeline Composer → Intake
- Related schema
- IntegrationReceiverRequest
- Next step
- /api/datasynch/processing/normalize, /api/datasynch/master-tables/import
POST/api/datasynch/master-tables/importMaster TablesGCP safeUI backed
Import master table records
Import mapper-safe dynamic records into CRM, locations, items, inventory, or telemetry.
- Required context
- companyId when enforced, workspaceId when available, manifestId, targetTable, records
- App surface
- DataSynch → Master Tables / Import
- Related schema
- ImportMasterTableRecordsRequest
- Next step
- /api/datasynch/runs, /api/datasynch/exceptions
POST/api/datasynch/locations/importLocationsGCP safeUI backed
Import location records
Import location master data from WMS, TMS, ERP, spreadsheet, partner feed, or integration connector.
- Required context
- manifestId, records
- App surface
- DataSynch → Locations
- Related schema
- ImportLocationRecordsRequest
- Next step
- /api/datasynch/geofences, /api/datasynch/processing/normalize
POST/api/datasynch/processing/normalizeProcessingGCP safeUI backed
Normalize records
Normalize mapper-safe records and infer fields before importing or evaluating rules.
- Required context
- manifestId, records
- App surface
- DataSynch → Processing
- Related schema
- NormalizeRecordsRequest
- Next step
- /api/datasynch/processing/map-fields, /api/datasynch/xref/evaluate
POST/api/datasynch/xref/evaluateXREFGCP safeUI backed
Evaluate XREF rules
Evaluate cross-reference rules against incoming records before import or dispatch.
- Required context
- manifestId, records, rules or profileId
- App surface
- DataSynch → XREF
- Related schema
- EvaluateXrefRulesRequest
- Next step
- /api/datasynch/master-tables/import, /api/datasynch/exceptions
POST/api/datasynch/geofencesGeofencesGCP safeUI backed
Create a geofence
Create a point-radius or polygon geofence tied to a manifest and optionally a location.
- Required context
- manifestId, name, geometryType
- App surface
- DataSynch → Geofences
- Related schema
- CreateGeofenceRequest
- Next step
- /api/datasynch/geofence-events, /api/datasynch/notification-dispatch
POST/api/datasynch/geofence-eventsGeofencesGCP safeUI backed
Create a geofence event
Record an enter, exit, dwell, wrong-site, or nearby event for a subject and geofence.
- Required context
- manifestId, eventType, subjectId or asset reference
- App surface
- DataSynch → Geofence Events
- Related schema
- CreateGeofenceEventRequest
- Next step
- /api/datasynch/exceptions, /api/datasynch/notification-dispatch
POST/api/datasynch/notification-dispatchDispatchGCP safeUI backed
Dispatch a notification
Queue or send internal notification, email, webhook, Slack message, or CSV export request.
- Required context
- manifestId, dispatchType, payload
- App surface
- DataSynch → Dispatch
- Related schema
- DispatchRequest
- Next step
- /api/datasynch/dispatch/logs
GET/api/datasynch/runsRunsGCP safeUI backed
List integration runs
List run logs for operational traceability and support.
- Required context
- manifestId
- App surface
- DataSynch → Runs / Telemetry Dashboard
- Related schema
- ListRunsResponse
- Next step
- /api/datasynch/runs/{runId}