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

# The support messenger's workspace and the caller's verified identity in it, or NULL when this deployment has no…

> The support messenger's workspace and the caller's verified identity in it, or NULL when this deployment has no messenger configured. The user hash is an HMAC over the user id, keyed with a secret no client can read, which is what stops a browser claiming to be somebody else.



## OpenAPI

````yaml /api-reference/openapi.json post /rpc/support_messenger
openapi: 3.0.0
info:
  description: ''
  title: >-
    The only schema PostgREST exposes. Reads are security_invoker views; writes
    are SECURITY DEFINER functions. Rebuilt wholesale on every deploy — it holds
    no data.
  version: 12.2.3
servers:
  - url: https://app.assetinfinity.ai/api
security: []
tags:
  - name: Signing in
  - name: Profile
  - name: My work
  - name: Sites and locations
  - name: Assets
  - name: Asset lifecycle
  - name: Asset components
  - name: Work lifecycle
  - name: Work order execution
  - name: Work sequencing
  - name: Maintenance
  - name: Inspections
  - name: Checklists
  - name: Verification
  - name: Self verification
  - name: Inventory
  - name: Inventory detail
  - name: Parts demand
  - name: Procurement
  - name: Vendors and contracts
  - name: Contracts
  - name: Amendments
  - name: Vendor spend forecast
  - name: Workforce
  - name: Workforce detail
  - name: Capacity
  - name: Dispatch
  - name: Shutdown
  - name: Permits
  - name: Tools
  - name: Tools on jobs
  - name: Bookings
  - name: Calibration history
  - name: Reliability
  - name: Sensors and meters
  - name: Readers
  - name: Trackers
  - name: Real-time location
  - name: Feeds
  - name: Energy
  - name: IT assets
  - name: IT asset software
  - name: IT asset topology
  - name: Map
  - name: Floor plans
  - name: Labels
  - name: Lost and found
  - name: Visitors
  - name: Root cause analysis
  - name: Costing
  - name: Finance
  - name: Budgets
  - name: Capex plans
  - name: FF&E plans
  - name: Documents
  - name: Document control
  - name: Document folders
  - name: Document tree
  - name: Knowledge
  - name: Reports
  - name: Dashboards
  - name: Extracts
  - name: Data exports
  - name: Audit center
  - name: Audit feed
  - name: Activity
  - name: Conversations
  - name: Notifications
  - name: Date reminders
  - name: Channels
  - name: Search
  - name: Copilot
  - name: Import
  - name: Bulk jobs
  - name: File exchange
  - name: Filing exceptions
  - name: Files
  - name: Sync
  - name: Support
  - name: API keys
  - name: Webhooks
  - name: MCP connections
  - name: MCP sign-in
  - name: SCIM provisioning
  - name: Directory sync
  - name: Security streams
  - name: Single sign-on
  - name: Two-factor sign-in
  - name: Admin
  - name: Access
  - name: Lookups
  - name: Read models
  - name: Reference
  - name: Reference columns
  - name: Reference entry
  - name: List views
  - name: Mapping
  - name: Numbering
  - name: Branding
  - name: Custom fields
  - name: Form studio
  - name: Workflows
  - name: Workflow studio
  - name: Rules
  - name: Statuses and transitions
  - name: Currencies and locales
  - name: Today
  - name: Work configuration
  - name: Asset configuration
  - name: Inventory configuration
  - name: Tool configuration
  - name: Workforce configuration
  - name: Vendor and contract configuration
  - name: Document configuration
  - name: Inspection configuration
  - name: Sites, locations and the organisation
  - name: Setup
  - name: Features
  - name: Billing
  - name: Licence
  - name: Welcome
  - name: Tray
  - name: Tenant switch
  - name: Release
  - name: Telegram
  - name: Inbound mail
  - name: Platform
externalDocs:
  description: PostgREST Documentation
  url: https://postgrest.org/en/v12/references/api.html
paths:
  /rpc/support_messenger:
    post:
      tags:
        - Support
      summary: >-
        The support messenger's workspace and the caller's verified identity in
        it, or NULL when this deployment has no…
      description: >-
        The support messenger's workspace and the caller's verified identity in
        it, or NULL when this deployment has no messenger configured. The user
        hash is an HMAC over the user id, keyed with a secret no client can
        read, which is what stops a browser claiming to be somebody else.
      parameters:
        - $ref: '#/components/parameters/preferParams'
      requestBody:
        content:
          application/json:
            schema:
              description: >-
                The support messenger's workspace and the caller's verified
                identity in it, or NULL when this deployment has no messenger
                configured. The user hash is an HMAC over the user id, keyed
                with a secret no client can read, which is what stops a browser
                claiming to be somebody else.
              type: object
          application/vnd.pgrst.object+json:
            schema:
              description: >-
                The support messenger's workspace and the caller's verified
                identity in it, or NULL when this deployment has no messenger
                configured. The user hash is an HMAC over the user id, keyed
                with a secret no client can read, which is what stops a browser
                claiming to be somebody else.
              type: object
          application/vnd.pgrst.object+json;nulls=stripped:
            schema:
              description: >-
                The support messenger's workspace and the caller's verified
                identity in it, or NULL when this deployment has no messenger
                configured. The user hash is an HMAC over the user id, keyed
                with a secret no client can read, which is what stops a browser
                claiming to be somebody else.
              type: object
          text/csv:
            schema:
              description: >-
                The support messenger's workspace and the caller's verified
                identity in it, or NULL when this deployment has no messenger
                configured. The user hash is an HMAC over the user id, keyed
                with a secret no client can read, which is what stops a browser
                claiming to be somebody else.
              type: object
        required: true
      responses:
        '200':
          description: OK
components:
  parameters:
    preferParams:
      description: Preference
      in: header
      name: Prefer
      required: false
      schema:
        enum:
          - params=single-object
        type: string

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.