Update Border Checkpoints

Update Sovereign Geo-Fencing, Data Rollbacks, Payload Batching, and Anomaly Detection.

POST/api/v1/connectors/dispatch

Request

curl -X POST "<BASE_URL>/api/v1/connectors/dispatch" \
  -H "Authorization: Bearer <ACCESS_TOKEN>" \
  -H "X-CQRS-Action: UPDATE_BORDER_CHECKPOINTS" \
  -H "Content-Type: application/json" \
  -H "X-Idempotency-Key: <IDEMPOTENCY_KEY>" \
  -d '{
    "binding_id": "7c9e6679-7425-40de-944b-e07fc1f90ae7"
  }'

Authorization

Minimum role: Tenant administratorThe caller must hold this role or a higher one.
Action: UPDATE_BORDER_CHECKPOINTS

Headers

AuthorizationstringRequired
Access token of the signed-in user, as a Bearer token. It identifies the user, their role and the workspace.
X-CQRS-ActionstringRequired
Names the command to run. Must be UPDATE_BORDER_CHECKPOINTS for this endpoint.
Content-TypestringRequired
Always application/json.
X-Idempotency-KeystringRequired
A key you choose that is unique to this attempt. A command repeated with the same key is not applied a second time.
X-Correlation-IdstringOptional
Your own identifier for the request. Returned in the x-correlation-id response header; generated when you leave it out.

Request body

binding_iduuidRequired
No description yet.
egress_anomaly_threshold_multipliernumber or nullOptional
No description yet.
execution_cadenceenum or nullOptional
Optimizes API billing and throughput for autonomous agents.
Allowed values
- REAL_TIME
- ADAPTIVE_MICRO_BATCHING
REAL_TIME
Legacy: Every AI action fires an immediate HTTP request.
ADAPTIVE_MICRO_BATCHING
100-Year: Intercepts high-volume AI actions and compiles them into a single /bulk-enrich API call, slashing third-party API costs.
geo_fencing_policyenum or nullOptional
Governs physical data residency compliance (Schrems II / GDPR).
Allowed values
- GLOBAL_UNRESTRICTED
- STRICT_DATA_SOVEREIGNTY
GLOBAL_UNRESTRICTED
Legacy: Blindly syncs all data regardless of the subject's residency.
STRICT_DATA_SOVEREIGNTY
100-Year: The Connector physically drops egress payloads for citizens whose data is legally forbidden from entering the connector's region.

Response

Status 202. The command was applied. The body is the record as it stands after the command: a JSON object whose fields depend on the record.

Errors

Every error carries an HTTP status. Where it also carries a code, branch on the code, not on the message.

400X-CQRS-Action is missing or names a command this route does not accept. Send UPDATE_BORDER_CHECKPOINTS.
400DOMAIN_ROUTINGThe body is not a valid command. Check the required fields and their types.
400IDEMPOTENCY_KEY_REQUIREDX-Idempotency-Key is missing.
401The access token is missing, expired or not valid.
401L1_AUTHThe caller's role is below tenantadmin or the caller has no access to this record.
403L1_POLICYA business rule refused the command. The message names the rule.
409L1_IDEMPOTENCYA command with this idempotency key was already applied.
409CONFLICTThe command would duplicate a record that must be unique.
500L3_COMMITThe command was valid but could not be saved.