Iridium Webhooks API

openapi: 3.2.0
info:
  title: Iridiumhqmcp Com Webhooks API
  version: 0.1.0
  description: 'Operations tagged webhooks across 2 of this provider''s published API definitions: openapi.json, iridiumhqmcp-com-openapi.json. Each path carries the servers of the definition it was published in.'
tags:
- name: Webhooks
paths:
  /webhook/unipile-account:
    post:
      tags:
      - Webhooks
      summary: Unipile Account Webhook
      description: Unipile posts here after a hosted-auth LinkedIn connection completes.
      operationId: unipile_account_webhook_webhook_unipile_account_post
      parameters:
      - name: user_id
        in: query
        required: false
        schema:
          anyOf:
          - type: string
          - type: 'null'
          title: User Id
      - name: token
        in: query
        required: false
        schema:
          anyOf:
          - type: string
          - type: 'null'
          title: Token
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
  /webhook/linkedin-message:
    post:
      tags:
      - Webhooks
      summary: Linkedin Message Webhook
      operationId: linkedin_message_webhook_webhook_linkedin_message_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /webhook/linkedin-relation:
    post:
      tags:
      - Webhooks
      summary: Linkedin Relation Webhook
      description: 'Unipile posts here when a connection invite is accepted (new_relation, registered

        with `source: "users"` — see ensure_relation_webhook, a separate hook from the message

        one above since Unipile scopes webhooks by source). Not real-time: Unipile''s own docs

        say up to 8h after LinkedIn accepts, since LinkedIn has no real-time event for this.'
      operationId: linkedin_relation_webhook_webhook_linkedin_relation_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /webhook/linkedin-account-status:
    post:
      tags:
      - Webhooks
      summary: Linkedin Account Status Webhook
      description: 'Unipile posts here on account lifecycle changes (registered with

        `source: "account_status"` — see ensure_account_status_webhook, a third hook

        separate from messaging/users since Unipile scopes webhooks by source).


        Payload shape: {"AccountStatus": {"account_id", "account_type", "message"}}

        (developer.unipile.com/docs/account-lifecycle). On a disruptive `message`

        (CREDENTIALS = invalid/missing credentials, or another restriction-type value —

        see _DISRUPTIVE_ACCOUNT_STATUS) this writes an ActionAudit row and logs loudly so

        the signal is captured (LIMITS.md A4 uses it to halve that day''s caps), and stamps

        user.unipile_status so services/linkedin_gate can turn the next LinkedIn call into a

        "reconnect" error instead of a silent failure against a dead account. A healthy message

        clears it back to None — this is what makes it self-heal once Unipile reports the account

        working again (e.g. RECONNECTED after the user reconnects).


        A `_READY_ACCOUNT_STATUS` message (OK/SYNC_SUCCESS) additionally clears

        user.unipile_syncing_since — the post-connect sync gate from ACCT_INITIALIZATION.md — and,

        only on that syncing→ready transition (never on a later steady-state `ok` for an account

        that was already ready), fires the two on-connect kickoffs

        (_kickoff_self_profile/_kickoff_chat_backfill) that used to run at connect time itself,

        before Unipile had necessarily finished setting the account up.'
      operationId: linkedin_account_status_webhook_webhook_linkedin_account_status_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
components:
  schemas:
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
  securitySchemes:
    HTTPBearer:
      type: http
      scheme: bearer
x-refined-from:
- openapi.json
- iridiumhqmcp-com-openapi.json
x-provenance:
  method: harvested
  publisher: Iridium
  source: https://api.iridiumhqmcp.com/openapi.json
  note: split by refine-openapis from the provider's own published document, verified by fetch (openapi/_original/*.fetch.json);
    stamped by stamp-openapi-provenance.py (roadmap#793)