How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Chili Piper

Chili Piper Meeting Type API

The meeting-type API from Chili Piper — 4 operation(s) for meeting-type.

Documentation Provider Profile APIs.io OpenAPI GitHub

Chili Piper Meeting Type API is one of 16 APIs that Chili Piper publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include meeting-type. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

This API exposes 7 operations across 4 paths, and defines 32 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://fire.chilipiper.com/api/fire-edge.

7 operations 4 paths 32 schemas 2 DELETE2 GET1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://fire.chilipiper.com/api/fire-edge
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Chili Piper Meeting Type API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (apiKeyAuth). By default, every request must be authenticated.

  • apiKeyAuth — API key in Authorization header. Format: 'Authorization: Bearer ' — the word 'Bearer' followed by a space and the key is required. Sending the key without the…

Paths & Operations 7

Across 4 paths, the API surfaces 7 operations — 2 DELETE, 2 GET, 1 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

meeting-type 7
POST
/v1/org/meeting-types
Create meeting type
meetingTypeCreate body → 200400default
GET
/v1/org/meeting-types/list
List meeting types
meetingTypeList 1 param → 200400default
GET
/v1/org/meeting-types/{meetingTypeId}
Get meeting type
meetingTypeGet 1 param → 200400default
PUT
/v1/org/meeting-types/{meetingTypeId}
Update meeting type
meetingTypeUpdate 1 param body → 200400default
DELETE
/v1/org/meeting-types/{meetingTypeId}
Remove meeting type
meetingTypeDelete 1 param → 200400default
PUT
/v1/org/meeting-types/{meetingTypeId}/reminders/{reminderId}
Attach reminder to meeting type
meetingTypeAttachReminder 2 params → 200400default
DELETE
/v1/org/meeting-types/{meetingTypeId}/reminders/{reminderId}
Detach reminder from meeting type
meetingTypeDetachReminder 2 params → 200400default

Schemas 32

The contract defines 32 schemas that model the data the API accepts and returns. The most detailed are MeetingType (13 properties), MeetingTypeUpdate (10 properties), MeetingTypeCreate (8 properties), Reminder (7 properties). Each schema is shown below with its type and property counts.

Reminder
object
7 properties 6 required
MeetingTypeId
string
SharedWith_Teams
object
2 properties 1 required
ReminderTriggerKind
string
MeetingLocation_TeamsMeetingLink
object
3 properties 3 required
MeetingLocation_AskTheGuest
object
2 properties 2 required
MeetingBookingLimitTimeframe
string
MeetingBookingLimitBy
string
MeetingTypeCreate
object
8 properties 3 required
ReminderTrigger
object
2 properties 1 required
MeetingLocation_ZoomOneTimeLink
object
3 properties 3 required
MeetingLocation_RingCentralLink
object
3 properties 3 required
MeetingBookingLimit
object
3 properties 3 required
WorkspaceId
string
MeetingLocation
MeetingTypeUpdate
object
10 properties
MeetingBuffers
object
2 properties
Map_String
object
MeetingType
object
13 properties 9 required
MeetingLocation_WebexLink
object
3 properties 3 required
SharedWith
MeetingLocation_GoToMeetingLink
object
3 properties 3 required
MeetingTypeStatus
string
MeetingLocation_GongLink
object
3 properties 3 required
MeetingLocation_HostsDefaultPhysicalLocation
object
3 properties 3 required
MeetingLocations
object
2 properties 1 required
MeetingLocation_HostsDefaultConferenceDetails
object
3 properties 3 required
MeetingLocation_DefinedInMeetingType
object
3 properties 2 required
ReminderChannel
string
MeetingLocationHost
string
MeetingLocation_CalendarPlatformConference
object
2 properties 2 required
SharedWith_Workspace
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

chili-piper-meeting-type-api-openapi.yml Raw ↑

Other APIs Chili Piper publishes across the network.

Chili Piper MCP Server
AE Profile APIs.io
Chili Piper Availability API
AE Profile APIs.io
Chili Piper Chat API
AE Profile APIs.io
Chili Piper Concierge API
AE Profile APIs.io
Chili Piper Distribution API
AE Profile APIs.io
Chili Piper Distro API
AE Profile APIs.io
Chili Piper Handoff API
AE Profile APIs.io
Chili Piper Meeting Type Reminder API
AE Profile APIs.io
Chili Piper Meetings API
AE Profile APIs.io
Chili Piper Rule API
AE Profile APIs.io
Chili Piper Scheduling Links API
AE Profile APIs.io
Chili Piper Team API
AE Profile APIs.io
#meeting-type
← Back to C APIs
API Details
ID
chili-piper:chili-piper-meeting-type-api
Base URL
https://fire.chilipiper.com/api/fire-edge
Docs
https://help.chilipiper.com/hc/en-us/articles/35576029581971-Edge-API-References
Provider
Chili Piper
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=chili-piper-meeting-type-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/chili-piper-meeting-type-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of Chili Piper Meeting Type API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.