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 Handoff API

The handoff API from Chili Piper — 3 operation(s) for handoff.

Documentation Provider Profile APIs.io OpenAPI GitHub

Chili Piper Handoff 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 Hand-off. 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 5 operations across 3 paths, and defines 34 schemas. It is described by OpenAPI 3.2.0, at version 1.287.2.

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

5 operations 3 paths 34 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

Chili Piper Handoff 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 5

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

handoff 5
GET
/v1/org/handoff/routers/handoff/list
Lists all handoff routers
handoffRouterList 1 param → 200400default
GET
/v1/org/handoff/routers/handoff/{routerId}
Get handoff router
handoffRouterGet 1 param → 200400default
PUT
/v1/org/handoff/routers/handoff/{routerId}
Update handoff router
handoffRouterUpdate 1 param body → 200400default
DELETE
/v1/org/handoff/routers/handoff/{routerId}
Remove handoff router
handoffRouterDelete 1 param → 200400default
POST
/v1/org/handoff/routers/handoff
Create handoff router
handoffRouterCreate body → 200400default

Schemas 34

The contract defines 34 schemas that model the data the API accepts and returns. The most detailed are RouteOutcome_Schedule (5 properties), RouterRoutingSummary (4 properties), HandoffRouter (4 properties), RoutingOutcome_Schedule (4 properties). Each schema is shown below with its type and property counts.

DistributionId
string
RoutingOutcome_OwnerAssign
object
1 property 1 required
HandoffRouter
object
4 properties 3 required
MeetingTypeId
string
RoutingOutcome_ContactOptions
object
1 property 1 required
RouteAssignment_User
object
2 properties 2 required
TimeoutRedirect_Landing
object
1 property 1 required
CrmAction_Notify
object
2 properties 1 required
RoutingCatchAllSummary
object
1 property 1 required
RouteTimeout
object
2 properties 2 required
RouteRow
object
2 properties 1 required
HandoffRouterId
string
HandoffRouterCreate
object
3 properties 3 required
RoutingOutcome_Other
object
2 properties 2 required
CrmAction_ConvertLead
object
1 property 1 required
WorkspaceId
string
RouteAssignment_Distribution
object
2 properties 2 required
TimeoutRedirect
RouterRouting
object
2 properties 1 required
RouterRoutingSummary
object
4 properties 2 required
RouteOutcome
RoutingOutcome_CrmAction
object
1 property 1 required
RoutingOutcome_Schedule
object
4 properties 1 required
Map_String
object
RouteAssignment
RoutingOutcome_Redirect
object
2 properties 1 required
RouteOutcome_Redirect
object
2 properties 2 required
RouteOutcome_Schedule
object
5 properties 3 required
TimeoutRedirect_Url
object
2 properties 2 required
HandoffRouterUpdate
object
2 properties
CrmAction
UserId
string
RoutingRowSummary
object
3 properties 1 required
RoutingOutcome

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

chili-piper-handoff-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 Meeting Type 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
#Hand-off
← Back to C APIs
API Details
ID
chili-piper:chili-piper-handoff-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-handoff-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/chili-piper-handoff-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 Handoff 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.