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

# Dismiss Meeting

> "Nothing to file this against" — the confirm card's other answer.

An internal or non-sales meeting has no account or deal, so it could never
be confirmed and sat in the review queue forever (2026-08-11). Dismissing
sets the context 'unresolvable' — the status the schema has carried for
exactly this since migration 142 — which removes it from both review-queue
predicates without touching them. Same caller's-own-client rule as
confirm: the dismissal is a human decision and must be attributed to the
human.



## OpenAPI

````yaml /openapi-generated.json post /meetings/{meeting_id}/dismiss
openapi: 3.1.0
info:
  title: anycrm-api
  version: 0.0.1
servers: []
security: []
tags:
  - name: Customer Intelligence
    description: >-
      Company research and ICP-fit scoring — create a research run, track its
      progress, and read back scored companies as leads.
  - name: Outreach
    description: >-
      The cold-email management console — domains, mailboxes, and campaigns — as
      a thin control plane over the SalesForge stack.
  - name: AnyCard
    description: >-
      Authenticated CRUD for AnyCard, the org's digital business-card /
      lead-capture product.
  - name: AnyCard Events
    description: >-
      Event-attribution analytics for AnyCard — which captured leads converted,
      broken down by source, owner, and deal.
  - name: AnyCard Share Links
    description: >-
      Unauthenticated endpoints reached by anyone who scans a QR code or opens a
      shared AnyCard link.
  - name: AI
    description: >-
      A streaming (SSE) AI chat endpoint with account-commit actions it can take
      on the caller's behalf.
  - name: Analytics Assistant
    description: >-
      The natural-language analytics assistant — a guarded text-to-SQL loop
      (SSE) that answers ad-hoc questions over the org's CRM data as a
      least-privilege, read-only database role.
  - name: Account Readiness
    description: >-
      Account Readiness Profiles — AI-scored signals on whether an account is
      ready for outreach or expansion, computed via a Temporal workflow.
  - name: Integrations
    description: >-
      Pipedream Connect — issuing connect tokens and managing the org's
      connected third-party accounts.
  - name: Feedback
    description: >-
      User-submitted platform feedback (bug reports, feature requests) — global,
      not scoped to one organization.
  - name: Public Media
    description: >-
      Unauthenticated image reads for publicly-embeddable assets (card photos,
      inline email images) — allowlisted by key shape; everything else in the
      storage bucket stays private.
  - name: Service Health
    description: Service liveness.
paths:
  /meetings/{meeting_id}/dismiss:
    post:
      tags:
        - Meetings
      summary: Dismiss Meeting
      description: >-
        "Nothing to file this against" — the confirm card's other answer.


        An internal or non-sales meeting has no account or deal, so it could
        never

        be confirmed and sat in the review queue forever (2026-08-11).
        Dismissing

        sets the context 'unresolvable' — the status the schema has carried for

        exactly this since migration 142 — which removes it from both
        review-queue

        predicates without touching them. Same caller's-own-client rule as

        confirm: the dismissal is a human decision and must be attributed to the

        human.
      operationId: dismiss_meeting_meetings__meeting_id__dismiss_post
      parameters:
        - name: meeting_id
          in: path
          required: true
          schema:
            type: string
            title: Meeting Id
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/DismissBody'
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
                title: Response Dismiss Meeting Meetings  Meeting Id  Dismiss Post
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      security:
        - HTTPBearer: []
components:
  schemas:
    DismissBody:
      properties:
        attend:
          anyOf:
            - type: string
            - type: 'null'
          title: Attend
        reopen:
          type: boolean
          title: Reopen
          default: false
      type: object
      title: DismissBody
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    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
  securitySchemes:
    HTTPBearer:
      type: http
      scheme: bearer

````