Avoma

Avoma Meeting Types API

The Meeting Types API from Avoma — 2 operation(s) for meeting types.

GitHub OpenAPI

Operations 5

GET /v1/meeting_type/ List Meeting Types #
POST /v1/meeting_type/ Create Meeting Type #
GET /v1/meeting_type/{uuid}/ Get Meeting Type #
PATCH /v1/meeting_type/{uuid}/ Update Meeting Type #
DELETE /v1/meeting_type/{uuid}/ Delete Meeting Type #

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/avoma/refs/heads/main/openapi/avoma-meeting-types-api-openapi.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/avoma:avoma-meeting-types-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

avoma-meeting-types-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  contact:
    email: help@avoma.com
    name: Avoma Help Center
  description: '# Introduction


    Welcome to Avoma''s developer hub.'
  title: Avoma Meeting Types API
  version: 1.0.0
servers:
- description: Avoma APIs
  url: https://api.avoma.com
security:
- bearerAuth: []
tags:
- name: Meeting Types
paths:
  /v1/meeting_type/:
    get:
      summary: List Meeting Types
      description: Returns all meeting types for the organization.
      tags:
      - Meeting Types
      parameters: []
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: ./openapi/components/external.yml#/components/schemas/meeting_type_response
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: ./openapi/components/external.yml#/components/schemas/http_error_response
      operationId: getV1MeetingType
      x-operation-id-source: derived
    post:
      summary: Create Meeting Type
      description: Creates a new meeting type for the organization.
      tags:
      - Meeting Types
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: ./openapi/components/external.yml#/components/schemas/meeting_type_request
      responses:
        '201':
          description: Created
          content:
            application/json:
              schema:
                $ref: ./openapi/components/external.yml#/components/schemas/meeting_type_response
        '400':
          description: Bad Request - Invalid data or duplicate label
          content:
            application/json:
              schema:
                $ref: ./openapi/components/external.yml#/components/schemas/http_error_response
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: ./openapi/components/external.yml#/components/schemas/http_error_response
      operationId: postV1MeetingType
      x-operation-id-source: derived
  /v1/meeting_type/{uuid}/:
    get:
      summary: Get Meeting Type
      description: Returns a specific meeting type by UUID.
      tags:
      - Meeting Types
      parameters:
      - name: uuid
        required: true
        in: path
        schema:
          type: string
          format: uuid
          description: Unique ID of the meeting type.
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: ./openapi/components/external.yml#/components/schemas/meeting_type_response
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                $ref: ./openapi/components/external.yml#/components/schemas/http_error_response
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: ./openapi/components/external.yml#/components/schemas/http_error_response
      operationId: getV1MeetingTypeByUuid
      x-operation-id-source: derived
    patch:
      summary: Update Meeting Type
      description: Updates a specific meeting type by UUID. You can provide either label or description (or both).
      tags:
      - Meeting Types
      parameters:
      - name: uuid
        required: true
        in: path
        schema:
          type: string
          format: uuid
          description: Unique ID of the meeting type.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: ./openapi/components/external.yml#/components/schemas/meeting_type_update_request
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: ./openapi/components/external.yml#/components/schemas/meeting_type_response
        '400':
          description: Bad Request - Invalid data
          content:
            application/json:
              schema:
                $ref: ./openapi/components/external.yml#/components/schemas/http_error_response
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                $ref: ./openapi/components/external.yml#/components/schemas/http_error_response
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: ./openapi/components/external.yml#/components/schemas/http_error_response
      operationId: patchV1MeetingTypeByUuid
      x-operation-id-source: derived
    delete:
      summary: Delete Meeting Type
      description: Deletes a specific meeting type by UUID.
      tags:
      - Meeting Types
      parameters:
      - name: uuid
        required: true
        in: path
        schema:
          type: string
          format: uuid
          description: Unique ID of the meeting type.
      responses:
        '204':
          description: No Content - Successfully deleted
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                $ref: ./openapi/components/external.yml#/components/schemas/http_error_response
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: ./openapi/components/external.yml#/components/schemas/http_error_response
      operationId: deleteV1MeetingTypeByUuid
      x-operation-id-source: derived
components:
  securitySchemes:
    bearerAuth:
      description: Avoma uses bearer token for authentication of the client. For now, you will have to contact [Avoma Support](mailto:help@avoma.com) to get one issued for you.
      scheme: bearer
      type: http