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 Launch Rule Components API

Manage the individual event, condition, and action components within rules.

Adobe Launch Rule Components API is one of 36 APIs that Adobe Launch publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 6 JSON Schema definitions.

Tagged areas include Rule Components. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, authentication docs, a getting-started guide, a changelog, and 6 JSON Schemas.

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

Requests are made against 2 base URLs: //reactor.adobe.io, https://reactor.adobe.io.

16 operations 10 paths 54 schemas 2 DELETE9 GET2 PATCH3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://reactor.adobe.io
Authentication
HTTP Bearer, API Key, API Key
Resource Areas
1

Authentication & Security 3

Adobe Launch Rule Components API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). An API key is passed in the header as x-api-key (apiKey). An API key is passed in the header as x-gw-ims-org-id (orgId).

  • bearerAuth — OAuth 2.0 access token for authenticated data collection via server.adobedc.net.
  • apiKey — Client ID credential from Adobe Developer Console.
  • orgId — Adobe Organization ID.

Paths & Operations 16

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

Rule components 16

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
POST
/properties/{propertyId}/rule_components
Create a Rule Component
createRuleComponent 1 param body → 201422
GET
/rules/{ruleId}/rule_components
List Rule Components for a Rule
listRuleComponentsForRule 8 params → 200
GET
/rule_components/{ruleComponentId}
Retrieve a Rule Component
getRuleComponent 1 param → 200404
PATCH
/rule_components/{ruleComponentId}
Update a Rule Component
updateRuleComponent 1 param body → 200404422
DELETE
/rule_components/{ruleComponentId}
Delete a Rule Component
deleteRuleComponent 1 param → 204404
GET
/rule_components/{ruleComponentId}/extension
Get the Extension for a Rule Component
getExtensionForRuleComponent 1 param → 200

Schemas 54

The contract defines 54 schemas that model the data the API accepts and returns. The most detailed are RuleComponentAttributes (13 properties), ExtensionAttributes (12 properties), ruleComponentsAttributes (9 properties), ExtensionResource (5 properties). Each schema is shown below with its type and property counts.

relatedProperty
object
1 property
ruleComponentsAttributes
object
9 properties
notesLookupResponse
notesCreatePayload
Relationship
object
2 properties
notesListResponse
rulesListResponse
RuleComponentAttributes
object
13 properties
metaList
object
1 property
ExtensionSingleResponse
object
1 property
ruleComponentsRulesListResponse
ruleComponentsNotesListResponse
dataCreateWithRelationships
object
1 property 1 required
ruleComponentsExtensionLookupResponse
ruleComponentsNotesCreatePayload
basicResourceProperties
object
2 properties
relatedUpdatedWithExtensionPackage
object
1 property
dataLookup
object
1 property
ruleComponentsNotesCreateResponse
ruleComponentsListResponse
ruleComponentsLookupResponse
relatedLibraries
object
1 property
ruleComponentsCreatePayload
RuleComponentUpdateRequest
object
1 property 1 required
RuleComponentCreateRequest
object
1 property 1 required
ruleComponentsOriginLookupResponse
ruleComponentsUpdateResponse
ruleComponentsUpdatePayload
ruleComponentsCreateAttributes
relatedExtension
object
1 property
relatedExtensionPackage
object
1 property
dataList
object
1 property
relatedRules
object
1 property
relatedNotes
object
1 property
notesAttributes
object
1 property 1 required
dataCreate
object
1 property 1 required
relatedRevisions
object
1 property
relatedUpdatedWithExtension
object
1 property
RuleComponentListResponse
object
2 properties
ruleComponentsCreateResponse
PaginationMeta
object
1 property
RuleComponentResource
object
5 properties
relatedResource
object
1 property
ExtensionResource
object
5 properties
ErrorResponse
object
1 property
extensionsEntity
relatedOrigin
object
1 property
RuleComponentSingleResponse
object
1 property
notesEntity
ExtensionAttributes
object
12 properties
extensionsLookupResponse
ruleComponentsRelationships
object
2 properties 1 required
dataUpdate
object
1 property 1 required
ruleComponentsEntity

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Adobe Launch publishes across the network.

Adobe Launch Builds API
Adobe Launch Callbacks API
Adobe Launch Companies API
Adobe Launch Data Elements API
Adobe Launch Edge Network API API
Adobe Launch Environments API
Adobe Launch Extension Packages API
Adobe Launch Extensions API
Adobe Launch Hosts API
Adobe Launch Libraries API
Adobe Launch Media Edge API API
Adobe Launch Properties API
Where this information came from

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