Promote a custom-activity property

Search Documentation

Search across all developer documentation

activity-properties

Promote a custom-activity property

POST /v1/activity-properties
Auth required api.activities.manage

Promotes a custom-activity property into the evaluable registry — registering (activity_name, property_name) → type so a Segment's SendQL predicate can reference it as activity.<activity>.<property>. enum_values is required when type is enum and rejected otherwise. An invalid name or type, or exceeding the per-activity promoted-property cap, returns 422 validation_failed.

Request body

Content type: application/json

activity_name string required

The custom activity whose property to promote; a lowercase identifier.

property_name string required

The property key to promote; a lowercase identifier.

type string enum required

One of: string, number, bool, datetime, enum

enum_values array<string> optional

Required when type is enum; must be empty/omitted otherwise.

description string optional

Responses

Errors follow the RFC 7807 problem format — see the error reference.

201 The promoted activity-property definition application/json
id string<uuid> required
activity_name string required

The custom activity whose property this promotes; a lowercase identifier.

property_name string required

The property key inside the activity's properties; a lowercase identifier.

type string enum required

One of: string, number, bool, datetime, enum

enum_values array<string> optional

Allowed values when type is enum; omitted otherwise.

description string required
origin string enum optional

Where the property is authored: managed (via the API/dashboard) or git (synced from a connected repo and read-only via the API).

One of: managed, git

source_path string optional

Repo-relative source file, for git-backed properties only.

last_synced_at string<date-time> optional

Time of the last git sync, for git-backed properties only.

created_at string<date-time> required
updated_at string<date-time> required
401 Missing, malformed, or unknown API key application/problem+json
403 Key lacks the required scope or plan limit violated application/problem+json
409 The mutation is rejected by a state rule rather than a bad request — e.g. editing a git-backed (read-only) definition. The code is conflict. application/problem+json
422 Query parameter or path value failed validation application/problem+json
429 Per-org rate limit exceeded application/problem+json
500 Unexpected server-side failure. The code is internal_error. The request_id field can be quoted to SendOps support to investigate. application/problem+json