> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sagescreen.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Get user data for Zapier

> Returns user profile, council info, and email preferences.
Accepts numeric WordPress user ID or UUID (`actor_id` meta).

Requires the `X-API-Key` header (Zapier API key).




## OpenAPI

````yaml /openapi/private/specs/wp/wp-webhooks.yml get /zapier/user/{user_id}
openapi: 3.1.0
info:
  title: >-
    SageScreen — Webhooks & CRM Integrations (Billing · Council · User · Deal ·
    Sage)
  version: 1.0.0
servers:
  - url: https://{domain}/wp-json/sagescreen/v1
    description: WordPress REST API
    variables:
      domain:
        default: api.sagescreen.app
security: []
tags:
  - name: Billing – Stripe
    description: Stripe webhook and subscription endpoints
  - name: Billing – Broadcast
    description: Postmark broadcast unsubscribe endpoint
  - name: Billing – Pipedrive
    description: Pipedrive CRM ID set-* webhook endpoints (called by Zapier)
  - name: Billing – AJAX
    description: Credit ledger, reactivation, and portal AJAX endpoints
  - name: Council – REST
    description: Zapier-facing REST endpoints for council data sync
  - name: Council – AJAX
    description: Council user and sage management AJAX endpoints
  - name: User – REST
    description: Zapier-facing REST endpoints
  - name: User – AJAX
    description: Council user management AJAX endpoints
  - name: User – Profile
    description: Self-service profile updates
  - name: Deal REST
    description: REST API endpoints authenticated via X-API-Key
  - name: Deal AJAX
    description: AJAX endpoints authenticated via WordPress nonce + capability check
  - name: Sage – REST
    description: REST API endpoints for sage operations and Python callbacks
  - name: Sage – CRUD
    description: AJAX endpoints for sage creation, editing, and status management
  - name: Sage – Build Workflow
    description: AJAX endpoints for the multi-step sage build process
paths:
  /zapier/user/{user_id}:
    get:
      tags:
        - User – REST
      summary: Get user data for Zapier
      description: |
        Returns user profile, council info, and email preferences.
        Accepts numeric WordPress user ID or UUID (`actor_id` meta).

        Requires the `X-API-Key` header (Zapier API key).
      operationId: zapierGetUser
      parameters:
        - name: user_id
          in: path
          required: true
          schema:
            type: string
            description: WordPress user ID (numeric) or actor_id UUID
            examples:
              - '42'
              - a1b2c3d4-e5f6-7890-abcd-ef1234567890
      responses:
        '200':
          description: User data retrieved
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ZapierUserResponse'
              example:
                success: true
                data:
                  user_id: 42
                  actor_id: a1b2c3d4-e5f6-7890-abcd-ef1234567890
                  email: john@example.com
                  first_name: John
                  last_name: Doe
                  display_name: John Doe
                  phone: '+15551234567'
                  council_id: c9d8e7f6-5a4b-3c2d-1e0f-a1b2c3d4e5f6
                  council_name: Greenville City Council
                  role: council_admin
                  email_product_updates: true
                  email_product_marketing: false
                  address_line1: 123 Main St
                  address_city: Greenville
                  address_state: SC
                  address_zip: '29601'
                  address_country: US
        '400':
          description: Invalid identifier format
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/UserPublicWPError'
              example:
                code: invalid_identifier
                message: Invalid user identifier format. Use numeric ID or UUID
                data:
                  status: 400
        '401':
          description: Missing or invalid API key
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/UserPublicWPError'
              example:
                code: invalid_api_key
                message: Invalid or missing API key
                data:
                  status: 401
        '404':
          description: User not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/UserPublicWPError'
              example:
                code: user_not_found
                message: >-
                  User not found for actor_id:
                  a1b2c3d4-e5f6-7890-abcd-ef1234567890
                data:
                  status: 404
        '500':
          description: API key not configured
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/UserPublicWPError'
              example:
                code: api_not_configured
                message: Zapier API key not configured
                data:
                  status: 500
      security:
        - apiKey: []
components:
  schemas:
    ZapierUserResponse:
      type: object
      properties:
        success:
          type: boolean
          const: true
        data:
          type: object
          properties:
            user_id:
              type: integer
              examples:
                - 42
            actor_id:
              type: string
              format: uuid
              examples:
                - a1b2c3d4-e5f6-7890-abcd-ef1234567890
            email:
              type: string
              format: email
              examples:
                - john@example.com
            first_name:
              type: string
              examples:
                - John
            last_name:
              type: string
              examples:
                - Doe
            display_name:
              type: string
              examples:
                - John Doe
            phone:
              type: string
              examples:
                - '+15551234567'
            council_id:
              type: string
              format: uuid
              examples:
                - c9d8e7f6-5a4b-3c2d-1e0f-a1b2c3d4e5f6
            council_name:
              type: string
              examples:
                - Greenville City Council
            role:
              type: string
              examples:
                - council_admin
            email_product_updates:
              type: boolean
              examples:
                - true
            email_product_marketing:
              type: boolean
              examples:
                - false
            address_line1:
              type: string
              examples:
                - 123 Main St
            address_city:
              type: string
              examples:
                - Greenville
            address_state:
              type: string
              examples:
                - SC
            address_zip:
              type: string
              examples:
                - '29601'
            address_country:
              type: string
              examples:
                - US
    UserPublicWPError:
      type: object
      description: Standard WordPress REST API error envelope
      required:
        - code
        - message
        - data
      properties:
        code:
          type: string
          examples:
            - user_not_found
        message:
          type: string
          examples:
            - User not found
        data:
          type: object
          required:
            - status
          properties:
            status:
              type: integer
              examples:
                - 404
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: X-API-Key
      description: SageScreen API key stored in `ss_zapier_api_key` option

````