Integrations and APIs
Integrations and APIs
Adobe Campaign Classic exposes SOAP web services and JSSP endpoints. A typical SOAP integration calls xtk:session#Logon with credentials and a security zone, receives a session token, then calls methods such as xtk:queryDef#ExecuteQuery, xtk:session#Write, or nms:delivery#SubmitDelivery. The token must be passed on later calls and expires according to session settings. Security zones, operator rights, and named rights apply to API calls just as they do in the client console.
ExecuteQuery returns XML; handle namespaces, encoding, and pagination explicitly. Write creates or updates records according to the schema and keys. Workflow APIs can start workflows or post signals, which is useful for event-driven integration. External accounts configure connections to file transfer, CRM, or other systems. Import and export activities move data in bulk, while JSSP and web applications provide HTTP endpoints for lighter integrations.
Traps and rule of thumb
Do not assume a successful logon means the operator can read the target schema. Do not build SQL or XML by string concatenation without escaping. A SOAP fault may be a business-rule rejection, not a transport error. Session tokens should not be logged.
Worked example: a CRM sends new contacts nightly: log on, call Write on a custom contact schema with an external ID as reconciliation key, then call a workflow signal to enrich and deduplicate. Rule: authenticate, validate rights, use schema keys for idempotency, and handle faults explicitly.