ClickSend messaging and contact API contracts.
Scope
Primary execution surface: server.
Developer Source Map
| Source | Reason |
|---|
| developers.clicksend.com | Event Contracts; Normalization Rules; Transport / Payload Rules; User Data Contracts; events, user data, transport |
RudderStack Cross-Check
RudderStack is used here only as secondary engineering evidence for discovery and cross-check.
| Destination | Type | Link |
|---|
clicksend | Discovery lead | source |
Verified Contracts
Event Contracts
| Object / Event | Field | Applies To | Type | Requirement | Exact Format | Normalization | Hashing | Examples | Caveat | Primary Source | Status | Confidence |
|---|
event | event_contract | server | object | Conditional | Platform event contract surface is documented on the referenced developer page. | Not clearly specified | Not clearly specified | - | Verified against vendor-owned developer documentation for this contract category. | developers.clicksend.com | Verified | High |
User Data Contracts
| Object / Event | Field | Applies To | Type | Requirement | Exact Format | Normalization | Hashing | Examples | Caveat | Primary Source | Status | Confidence |
|---|
user | user_data_contract | server | object | Conditional | Platform user/profile identifier contract surface is documented on the referenced developer page. | Not clearly specified | Not clearly specified | - | Verified against vendor-owned developer documentation for this contract category. | developers.clicksend.com | Verified | High |
Transport / Payload Rules
| Object / Event | Field | Applies To | Type | Requirement | Exact Format | Normalization | Hashing | Examples | Caveat | Primary Source | Status | Confidence |
|---|
request | endpoint | server | object | Required | ClickSend REST v3 uses Basic authentication and JSON request bodies. | Not clearly specified | Not clearly specified | - | Verified against vendor-owned developer documentation for this contract category. | developers.clicksend.com | Verified | High |
Candidate / Needs Review Items
Normalization Rules
| Object / Event | Field | Applies To | Type | Requirement | Exact Format | Normalization | Hashing | Examples | Caveat | Primary Source | Status | Confidence |
|---|
normalization | normalization_contract | server | string | Optional | Not clearly specified in one canonical row-level contract; see blocker/caveat. | Not clearly specified | Not clearly specified | - | Blocker: normalization_contract_missing — Fallback/precedence rules are implementation logic not explicitly canonicalized by vendor docs. | developers.clicksend.com | Needs manual review | Medium |
Excluded Items
| Object / Event | Field | Caveat | Primary Source | Status | Confidence |
|---|
normalization | hashing_contract | Excluded: row_definition_missing — Investigated, but not supportable strongly enough for verified publication. | developers.clicksend.com | Excluded | Low |
Last Reviewed
2026-03-31