Condition catalog
List the person attributes and computed attributes available for DECISION and CASE CONDITIONS, plus the custom object types. Attribute tokens are ready to use as condition selection paths (e.g. attributes.plan, computed.ltv). NOTE: these attributes.* tokens are ONLY for DECISION/CASE conditions — SEND_MESSAGE template bindings use a different syntax (person.<key>); call journeys_message_variables for those. Also describes the cdp_predicate DECISION condition term shape: which op values are legal per attribute type (operatorsByType), and which value shape each op expects (cdpPredicateValueShapes).
Authorizations
Organization API key, sent as Authorization: Bearer boom_org_....
Response
Success
Conversation-recency paths for a DECISION value condition. A CLOSED set — any other key under engagement.conversation. is refused at publish, because a blank resolve there would read as 0 and open a gate that should be shut. Not available to CASE. This list is the DECISION view only: the same root also carries id and inboxUrl, which resolve in an HTTP_REQUEST node and are refused in a condition (nothing compares usefully against an id, and a numeric op would coerce it to 0 and take the branch).
Legal op values for a cdp_predicate condition term, keyed by its type.
Explains a cdp_predicate term's fields and the value shape each op expects.