DealSleek API · Connectors
PreviewUpdate Data Governance Policy
Update PII Masking, Conflict Resolution, and Rate Limit routing policies.
/api/v1/connectors/dispatchHeaders
AuthorizationstringRequiredAccess token of the signed-in user, as a Bearer token. It identifies the user, their role and the workspace.
X-CQRS-ActionstringRequiredNames the command to run. Must be
UPDATE_DATA_GOVERNANCE_POLICYfor this endpoint.Content-TypestringRequiredAlways
application/json.X-Idempotency-KeystringRequiredA key you choose that is unique to this attempt. A command repeated with the same key is not applied a second time.
X-Correlation-IdstringOptionalYour own identifier for the request. Returned in the
x-correlation-idresponse header; generated when you leave it out.
Request body
binding_iduuidRequiredNo description yet.
conflict_resolution_strategyenum or nullOptionalDefines what happens when bidirectional syncs collide (e.g. human updated HubSpot, but a bot just updated the Facebook Lead Form).
- Allowed values
- EXTERNAL_WINS
- INTERNAL_WINS
- AGENTIC_EVALUATION
- EXTERNAL_WINS
- The external platform's payload overwrites DealSleek data.
- INTERNAL_WINS
- DealSleek's data prevents the external update from applying.
- AGENTIC_EVALUATION
- 100-Year: An AI agent reads the ReasoningTraces and AgenticMemory to determine which data source has higher confidence, then applies the winning value.
egress_pii_maskingenum or nullOptionalDefines how PII is handled before it leaves the DealSleek network via this connector.
- Allowed values
- ALLOW_ALL
- REDACT_PII
- HASH_IDENTITY
- ALLOW_ALL
- Send data exactly as it exists in the CRM.
- REDACT_PII
- Replace PII fields (SSN, phone, address) with [REDACTED] or generic masks.
- HASH_IDENTITY
- Hash sensitive identifiers (e.g., SHA256 of email) so the external system can match records without knowing the raw plaintext value.
priority_routing_enabledboolean or nullOptionalNo description yet.
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.
- 400
X-CQRS-Actionis missing or names a command this route does not accept. SendUPDATE_DATA_GOVERNANCE_POLICY. - 400
DOMAIN_ROUTINGThe body is not a valid command. Check the required fields and their types. - 400
IDEMPOTENCY_KEY_REQUIREDX-Idempotency-Keyis missing. - 401The access token is missing, expired or not valid.
- 401
L1_AUTHThe caller's role is belowtenantadminor the caller has no access to this record. - 403
L1_POLICYA business rule refused the command. The message names the rule. - 409
L1_IDEMPOTENCYA command with this idempotency key was already applied. - 409
CONFLICTThe command would duplicate a record that must be unique. - 500
L3_COMMITThe command was valid but could not be saved.