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

Chili Piper Rule API

The rule API from Chili Piper — 2 operation(s) for rule.

Chili Piper Rule 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 rule. 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 2 operations across 2 paths, and defines 81 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.

2 operations 2 paths 81 schemas 1 GET1 POST

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 Rule 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 2

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

rule 2
GET
/v1/org/rule/list
List rules
ruleList 4 params → 200400default
POST
/v1/org/rule
Create rule
ruleCreate body → 200400default

Schemas 81

The contract defines 81 schemas that model the data the API accepts and returns. The most detailed are RuleView_OwnershipRule (9 properties), OwnershipRule (9 properties), RuleView_NonOwnershipRule (8 properties), NonOwnershipRule (8 properties). Each schema is shown below with its type and property counts.

RelatedDataObject
string
Related object path in slash-separated string format: / /.../topObject. The topObject is the last segment; relations precede it. Example: "Account/Lead" means…
RuleCreateRequest
object
1 property 1 required
OwnershipConditionsRequest_SingleParameterCondition
object
4 properties 4 required
Evaluable_RelativeDay
object
4 properties 3 required
Evaluable_RelativeMonth
object
4 properties 3 required
NonOwnershipConditionsRequest_ValueCondition
object
5 properties 5 required
Option_OwnershipReference
Option_ChiliProduct
OwnershipConditionsRequest
NonOwnershipConditionsRequest_2
Evaluable_RelativeYear
object
4 properties 3 required
EvaluableCondition
object
5 properties 5 required
Operator
string
ValueCondition
object
5 properties 5 required
OwnershipConditionsRequest_ObjectExistsCondition
object
4 properties 4 required
OwnershipConditionsRequest_OwnershipCondition
object
5 properties 2 required
NonOwnershipConditionsRequest_EvaluableCondition
object
5 properties 5 required
ConditionId
string
OwnershipConditionsRequest_ConditionGroup
object
5 properties 4 required
RelatedChildObjectRef
string
OwnershipConditionsRequest_2
ObjectExistsCondition
object
4 properties 4 required
LogicalOperator
string
RelativeWeek
object
4 properties 3 required
PaginatedResult_RuleView
object
4 properties 3 required
StaticValue
RuleView_OwnershipRule
object
9 properties 7 required
CreateRuleDto_CreateRuleRequest
object
5 properties 4 required
DataSource
string
SingleOperator
string
NonEmptyList_NonOwnershipConditionsRequest
array
OwnershipConditionsRequest_StaticValueCondition
object
5 properties 5 required
RuleId
string
RelativeQuarter
object
4 properties 3 required
WorkspaceId
string
StaticValueCondition
object
5 properties 5 required
Evaluable_2
NonOwnershipConditionsRequest_SingleParameterCondition
object
4 properties 4 required
DataObject
SearchOwnershipByDTO
string
NonOwnershipConditionsRequest_ObjectExistsCondition
object
4 properties 4 required
CallerRef
string
stringified caller reference in format $type/$id
TeamId
string
Option_TeamId
OwnershipCondition
object
5 properties 2 required
Option_String
string
CustomMatchedObjectRef
string
custom matched object ref - format: $id$tpe available types: LeadToAccountMatchingConfigType,ContactToDuplicateContactMatchingConfigType,LeadToDuplicateContact…
OwnershipReference
object
3 properties 3 required
NonOwnershipRule
object
8 properties 7 required
OwnershipRule
object
9 properties 7 required
NormalDataObject
string
Standard CRM object name, e.g. "Account", "Contact", "Lead", "Opportunity", "Case". Use for direct conditions on any Salesforce/CRM object. Do NOT use MatchedA…
NonOwnershipConditionsRequest_ConditionGroup
object
5 properties 4 required
RelativeDay
object
4 properties 3 required
Evaluable_RelativeWeek
object
4 properties 3 required
DataObjectReference
object
2 properties 2 required
CreateRuleDto_CreateOwnershipRuleRequest
object
6 properties 4 required
MatchedObject
string
Matched/related-object reference from a matching configuration (e.g. MatchedAccount = account matched via Lead-to-Account config). NOT for ordinary Salesforce…
ChiliProduct
string
RelativeMonth
object
4 properties 3 required
OwnershipConditionsRequest_ValueCondition
object
5 properties 5 required
ConditionGroup
object
5 properties 4 required
RuleView_2
DataReference
object
3 properties 3 required
RuleView
SimpleMetadata
object
5 properties 5 required
NonOwnershipConditionsRequest
Evaluable_RelativeQuarter
object
4 properties 3 required
DataField
string
NonOwnershipConditionsRequest_StaticValueCondition
object
5 properties 5 required
RelativeYear
object
4 properties 3 required
RuleView_NonOwnershipRule
object
8 properties 7 required
NonEmptyList_OwnershipConditionsRequest
array
Option_RuleId
ConditionGroupId
string
ConditionGroup1
object
5 properties 4 required
CreateRuleDto
Map_String
object
OwnershipConditionsRequest_EvaluableCondition
object
5 properties 5 required
Evaluable
RuleBuilderVersion
string
SingleParameterCondition
object
4 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

chili-piper-rule-api-openapi.yml Raw ↑

Other APIs Chili Piper publishes across the network.

Chili Piper MCP Server
Chili Piper Availability API
Chili Piper Chat API
Chili Piper Concierge API
Chili Piper Distribution API
Chili Piper Distro API
Chili Piper Handoff API
Chili Piper Meeting Type API
Chili Piper Meeting Type Reminder API
Chili Piper Meetings API
Chili Piper Scheduling Links API
Chili Piper Team API
Where this information came from

This is an independent, third-party profile of Chili Piper Rule 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.