clix-api-triggered-campaigns

To trigger API campaigns from a backend service, configure dynamic payloads using trigger.* properties for personalized targeting and templates. The setup enforces plan validation, strict snake_case key naming, and safety constraints to ensure reliable, auditable delivery of transactional and workflow messages.

API-triggered transactional messages require authentication through X-Clix-Project-ID and X-Clix-API-Key headers. Your backend service must include these credentials in requests to validate access and trigger campaigns configured in the Clix console.

Yes, you can use Python or Node.js to send API-triggered campaign requests. The setup includes quick-start samples in both languages demonstrating how to construct backend requests with dynamic payloads to trigger test campaigns.

Backend API-triggered campaigns enforce strict payload constraints including a maximum of 3 dynamic attributes, mandatory snake_case key naming, and non-PII data requirements. These safety constraints enforce reliable, auditable delivery and plan validation.

Audience targeting for API-triggered campaigns works by applying audience rules alongside dynamic trigger.* properties within your payload. This combination allows backend services to send personalized transactional and workflow messages based on the configured template.

API-triggered campaign payloads fail validation if they violate strict safety constraints. Ensure your payload uses snake_case keys, contains no PII data, includes a maximum of 3 dynamic attributes, and conforms to the api-trigger-plan.json validation script rules.