> ## Documentation Index > Fetch the complete documentation index at: https://docs.gaintrace.com/llms.txt > Use this file to discover all available pages before exploring further. # Create a survey segment > Save a segment of Company and People rules. Use it as a survey's in-app audience (`settings.inApp.targeting.audience.segmentId`) or as the audience of an invitation request (`segmentId`). The name must be unique in the workspace, ignoring case; a name already in use returns `422`. A segment needs at least one rule across the two groups. Requires a secret server key (`gt_live_`). Publishable keys (`gt_pub_`) return `403`. **Scope:** `write:surveys` ## OpenAPI ````yaml /openapi.json post /survey-segments openapi: 3.1.0 info: title: GainTrace API version: 1.0.0 description: >- The GainTrace REST API (v1). Read your customer data and push product-usage events, metric events, and signals into GainTrace. All endpoints are authenticated with a Bearer API key and scoped to a single workspace. Each API key can send 60 requests a minute. A `429` response includes a `Retry-After` header with the seconds to wait. servers: - url: https://app.gaintrace.com/api/v1 description: Production security: - bearerAuth: [] tags: - name: Companies description: Read and manage canonical company records. - name: Signals description: Read, create, and manage buyer / risk signals. - name: Ingest description: Push product-usage and metric events into GainTrace. - name: Contacts description: >- The original path for People. It shares its handlers with /people, and also offers delete-by-key. - name: Webhooks description: Subscribe to workspace events with signed, retried delivery. - name: People description: Read and manage People. One Person can belong to many Companies. - name: NPS responses description: Import NPS scores from another survey tool and read your NPS history. - name: Surveys description: >- Create and launch surveys, request invitations, record responses and mint in-app sessions. - name: Survey responses description: Read the responses collected by your surveys. - name: Survey segments description: Save groups of Companies and People that surveys can target. - name: Survey imports description: Pull responses from the survey tools your workspace has connected. paths: /survey-segments: post: tags: - Survey segments summary: Create a survey segment description: >- Save a segment of Company and People rules. Use it as a survey's in-app audience (`settings.inApp.targeting.audience.segmentId`) or as the audience of an invitation request (`segmentId`). The name must be unique in the workspace, ignoring case; a name already in use returns `422`. A segment needs at least one rule across the two groups. Requires a secret server key (`gt_live_`). Publishable keys (`gt_pub_`) return `403`. **Scope:** `write:surveys` operationId: createSurveySegment requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/SurveySegmentCreate' example: name: Enterprise decision makers rules: company: logic: and rules: - field: segment operator: eq value: enterprise person: logic: and rules: - field: contactRole operator: is_any_of value: - decision_maker - executive_sponsor responses: '201': description: Segment saved. content: application/json: schema: type: object required: - data properties: data: $ref: '#/components/schemas/SurveySegment' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '422': $ref: '#/components/responses/UnprocessableEntity' '429': $ref: '#/components/responses/RateLimited' '500': $ref: '#/components/responses/InternalServerError' '503': $ref: '#/components/responses/ServiceUnavailable' '504': $ref: '#/components/responses/GatewayTimeout' components: schemas: SurveySegmentCreate: type: object required: - name - rules additionalProperties: false properties: name: type: string minLength: 1 maxLength: 120 description: Unique in the workspace, ignoring case. rules: $ref: '#/components/schemas/SurveyAudienceRules' SurveySegment: type: object required: - id - name - company - person - createdAt - updatedAt properties: id: type: string format: uuid name: type: string company: $ref: '#/components/schemas/SurveyFilterGroup' person: $ref: '#/components/schemas/SurveyFilterGroup' createdAt: type: string format: date-time updatedAt: type: string format: date-time SurveyAudienceRules: type: object required: - company - person additionalProperties: false description: >- Who to reach: People who match `person`, at Companies that match `company`. An empty `rules` list in a group matches everyone for that group. A request needs at least one rule across both groups, so nobody is ever invited by accident. Only People with an email address at Companies that aren't archived can match. properties: company: $ref: '#/components/schemas/SurveyFilterGroup' person: $ref: '#/components/schemas/SurveyFilterGroup' SurveyFilterGroup: type: object required: - logic - rules additionalProperties: false properties: logic: type: string enum: - and - or rules: type: array maxItems: 20 items: $ref: '#/components/schemas/SurveyFilterRule' Error: type: object required: - error description: The standard error envelope. Every 4xx/5xx response uses this shape. properties: error: type: object required: - code - message properties: code: type: string enum: - bad_request - unauthorized - payment_required - forbidden - not_found - conflict - unprocessable_entity - rate_limit_exceeded - internal_server_error - service_unavailable - gateway_timeout description: >- Stable, machine-readable error code. Each code maps to exactly one HTTP status. message: type: string description: >- Human-readable, safe description of what went wrong. Never contains internal or provider detail. doc_url: type: string format: uri example: https://docs.gaintrace.com/errors#not_found description: Deep link to this code in the Errors reference. SurveyFilterRule: type: object required: - field - operator - value additionalProperties: false properties: field: type: string minLength: 1 maxLength: 120 description: >- In a Company rule group, a field key from your Company data model, such as `segment` or `plan`. In a People rule group, one of `email`, `name`, `role`, `contactRole`, `isChampion`, `lastSeenAt`, `engagementScore`, `createdAt`, or `traits.` for a Person trait. `person.` and `people.` prefixes are accepted. Any other People field returns `422`. operator: type: string enum: - eq - neq - gt - gte - lt - lte - contains - not_contains - starts_with - ends_with - is_empty - is_not_empty - in - not_in - between - before - after - in_the_last - in_the_next - older_than - further_than - is - is_not - is_any_of - is_none_of description: The same operators Flow conditions use. value: oneOf: - type: string maxLength: 500 - type: number - type: boolean - type: array maxItems: 50 items: type: string maxLength: 200 value2: oneOf: - type: string maxLength: 500 - type: number description: The upper bound for `between`. unit: type: string enum: - minutes - hours - days - workdays - weeks - months description: The unit for date operators such as `in_the_last`. responses: BadRequest: description: The request could not be parsed (for example, malformed JSON). content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: bad_request message: Invalid JSON body doc_url: https://docs.gaintrace.com/errors#bad_request Unauthorized: description: Missing, malformed, expired, or revoked API key. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: unauthorized message: Missing Authorization header doc_url: https://docs.gaintrace.com/errors#unauthorized Forbidden: description: >- The key is valid but lacks the required scope, the origin is not allowed, or API v1 is not enabled for the workspace. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: forbidden message: 'Insufficient scope: write:companies required' doc_url: https://docs.gaintrace.com/errors#forbidden UnprocessableEntity: description: The request was well-formed but a value failed validation. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: unprocessable_entity message: 'Request validation failed. name: name is required' doc_url: https://docs.gaintrace.com/errors#unprocessable_entity RateLimited: description: >- The per-key rate limit was exceeded. Each API key can send 60 requests per minute, counted in calendar-minute windows. The `Retry-After` header gives the whole seconds (1 to 60) until the next window opens. Wait that long, then retry. headers: Retry-After: description: Whole seconds until the next one-minute window starts. schema: type: integer minimum: 1 maximum: 60 example: 23 content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: rate_limit_exceeded message: >- Can't accept more than 60 requests a minute from one API key. Retry in 23 seconds. doc_url: https://docs.gaintrace.com/errors#rate_limit_exceeded InternalServerError: description: >- An unexpected error occurred on our side. The failure is logged; retry shortly. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: internal_server_error message: Something went wrong. Try again in a moment. doc_url: https://docs.gaintrace.com/errors#internal_server_error ServiceUnavailable: description: >- A backing service (for example, the database) was temporarily unavailable. Retry shortly. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: service_unavailable message: We had trouble reaching the database. Try again in a moment. doc_url: https://docs.gaintrace.com/errors#service_unavailable GatewayTimeout: description: >- The request took too long upstream before completing. Retry, and reduce batch size for large payloads. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: code: gateway_timeout message: The request timed out. Try again in a moment. doc_url: https://docs.gaintrace.com/errors#gateway_timeout securitySchemes: bearerAuth: type: http scheme: bearer description: >- 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. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.