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

Adobe Suite Rule components API

Rule components are the individual items that make up a rule. Rule components have three basic types: events (what triggers a rule), conditions (what the rule checks to determine an action), and actions (what the rule executes depending on whether the condition is met). A rule component can **only** belong to exactly one rule.

Adobe Suite Rule components API is one of 482 APIs that Adobe Suite publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Rule Components. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, pricing, release notes, and a getting-started guide.

This API exposes 10 operations across 6 paths, and defines 42 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, //reactor.adobe.io.

10 operations 6 paths 42 schemas 1 DELETE6 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://image.adobe.io
Resource Areas
1

Paths & Operations 10

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

Rule components 10

Rule components are the individual items that make up a rule. Rule components have three basic types: events (what triggers a rule), conditions (what the rule checks to determine…

GET
/rules/{RULE_ID}/rule_components
List a rule's components
listRuleComponents 17 params → 200
POST
/rules/{RULE_ID}/rule_components
Create a new rule component
createRuleComponent 5 params body → 201
GET
/rule_components/{RULE_COMPONENT_ID}
Retrieve a rule component
retrieveRuleComponent 5 params → 200
DELETE
/rule_components/{RULE_COMPONENT_ID}
Delete a rule component
deleteRuleComponent 4 params → 204
PATCH
/rule_components/{RULE_COMPONENT_ID}
Update a rule component
updateRuleComponent 5 params body → 200
GET
/rule_components/{RULE_COMPONENT_ID}/extension
Look up the extension that provides a specific rule component.
getRuleComponentExtension 8 params → 200
GET
/rule_components/{RULE_COMPONENT_ID}/origin
Retrieve a rule component's origin
retrieveRuleComponentOrigin 8 params → 200
GET
/rule_components/{RULE_COMPONENT_ID}/rules
List the rules that utilize a rule component
listRuleComponentsRelatedRules 10 params → 200
GET
/rule_components/{RULE_COMPONENT_ID}/notes
List a rule component's notes
listRuleComponentNotes 10 params → 200
POST
/rule_components/{RULE_COMPONENT_ID}/notes
Create a note for a rule component
createRuleComponentNote 5 params body → 201

Schemas 42

The contract defines 42 schemas that model the data the API accepts and returns. The most detailed are ruleComponentsAttributes (9 properties), ruleComponentsRelationships (2 properties), basicResourceProperties (2 properties), dataCreate (1 property). Each schema is shown below with its type and property counts.

ruleComponentsNotesCreateResponse
relatedUpdatedWithExtension
object
1 property
relatedExtension
object
1 property
metaList
object
1 property
ruleComponentsEntity
extensionsEntity
notesLookupResponse
ruleComponentsCreateResponse
relatedResource
object
1 property
dataUpdate
object
1 property 1 required
dataLookup
object
1 property
relatedExtensionPackage
object
1 property
ruleComponentsRulesListResponse
relatedOrigin
object
1 property
ruleComponentsListResponse
relatedLibraries
object
1 property
ruleComponentsNotesCreatePayload
relatedProperty
object
1 property
relatedRules
object
1 property
rulesListResponse
ruleComponentsUpdatePayload
ruleComponentsLookupResponse
notesAttributes
object
1 property 1 required
relatedUpdatedWithExtensionPackage
object
1 property
dataList
object
1 property
ruleComponentsAttributes
object
9 properties
basicResourceProperties
object
2 properties
relatedRevisions
object
1 property
ruleComponentsUpdateResponse
ruleComponentsNotesListResponse
ruleComponentsExtensionLookupResponse
relatedNotes
object
1 property
ruleComponentsOriginLookupResponse
dataCreateWithRelationships
object
1 property 1 required
notesCreatePayload
dataCreate
object
1 property 1 required
ruleComponentsCreateAttributes
notesListResponse
notesEntity
extensionsLookupResponse
ruleComponentsCreatePayload
ruleComponentsRelationships
object
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

adobe-suite-rule-components-api-openapi.yml Raw ↑

Other APIs Adobe Suite publishes across the network.

Adobe Sign API
Adobe Experience Manager API
Adobe Stock API
Adobe Premiere Pro API
Adobe After Effects API
Adobe Target API
Adobe Campaign API
Adobe User Management API
Adobe I/O Events API
Adobe MCP Servers
Adobe Suite Accelerated Queries API
Adobe Suite Access Control Policies API
Where this information came from

This is an independent, third-party profile of Adobe Suite Rule components 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.