Request survey invitations
Request email invitations for up to 100 people (personIds), or for everyone a saved segment (segmentId) or a set of Company and People rules (audience) matches, up to 1,000 people. The survey must be active.
Send or approve. Workspaces send by default: each invitation is released to send right away, or at the survey’s next send window. A workspace can switch to approval, where invitations wait in Triage until a teammate approves them, and approvals expire after 14 days. The result’s mode says which applied. Invitations sent by an API key follow the workspace setting.
Who is skipped. People are skipped, not failed, when an invitation for their email already waits or is about to send, when they are inside the survey’s cooldownDays, or when the workspace frequency rule applies. The response counts them but does not name them. To preview who would be invited, use the gt_survey_request_invitations MCP tool, which defaults to a dry run.
Errors. With personIds, every person must be active, have an email address and belong to a Company, or the whole request returns 400 and nothing is queued. A segmentId that is missing or archived returns 404. An audience that matches more than 1,000 people returns 400: narrow the rules or split them into segments. An audience with no rules, or a body with more than one of the three keys, returns 422. Requires a secret server key (gt_live_). Publishable keys (gt_pub_) return 403.
Scope: write:surveys
Authorizations
Bearer API key. Secret server keys start with gt_live_; client-safe browser keys start with gt_pub_ (write-only, origin-pinned). Create and scope keys in Settings → API Keys.
Path Parameters
The survey's UUID.
Body
- Option 1
- Option 2
- Option 3
Who to invite. Send exactly one of personIds, segmentId or audience.
Ids of people. Duplicates are ignored.
1 - 100 elementsResponse
Invitations accepted.