Call the Decisioning API
Call the Decisioning API from your own app or website to get a personalization decision — who qualifies and what content to show — back in real time, over plain HTTP. Use the authenticated flow server-side and the unauthenticated flow for public web pages.
Authenticated request (server-side)
- Obtain an OAuth access token for your connected app (see connected-app authentication).
- Send a
Bearer-authenticated request naming the personalization point and the individual. - Parse the response for the decision’s content and merge fields.
- Render that content in your app, or log the decision for later analysis.
curl -X POST "{{instance_url}}/personalization/decisioning" \
-H "Authorization: Bearer {{access_token}}" \
-H "Content-Type: application/json" \
-d '{ "pointId": "{{point_id}}", "individualId": "{{individual_id}}" }' {
"pointId": "{{point_id}}",
"decisionId": "{{decision_id}}",
"content": {
"template": "{{template_name}}",
"mergeFields": { "{{field_name}}": "{{field_value}}" }
}
} Unauthenticated request (public web)
For public web, the Website connector’s SDK calls an unauthenticated decisioning endpoint scoped to your connector — no user token, but still rate-limited. Use this path for anonymous, on-page personalization rather than calling the authenticated endpoint from the browser.
Decisioning API — Postman collection
Discussion
Comments are not configured for local development. They appear once the site owner connects GitHub Discussions (Giscus).