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

Manage server-side event forwarding rules.

Adobe Launch Rules 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 Rules. 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 23 operations across 15 paths, and defines 71 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.

23 operations 15 paths 71 schemas 2 DELETE15 GET2 PATCH4 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 Rules 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 23

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

Rules 23

Rules control the behavior of the resources contained in a deployed library. A rule is a group of one or more rule components, and exists to tie the rule components together in a…

GET
/properties/{PROPERTY_ID}/rules
List a property's rules
listRules 16 params → 200
POST
/properties/{PROPERTY_ID}/rules
Create a rule
createRule 5 params body → 201
GET
/rules/{RULE_ID}
Retrieve a rule
retrieveRule 5 params → 200
DELETE
/rules/{RULE_ID}
Delete a rule
deleteRule 4 params → 204
PATCH
/rules/{RULE_ID}
Update a rule
updateRule 5 params body → 200
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
/rules/{RULE_ID}/libraries
List all libraries that use a specific rule
listRuleLibraries 7 params → 200
GET
/rules/{RULE_ID}/property
Retrieve the property that owns a specific rule
retrieveRuleProperty 5 params → 200
GET
/rules/{RULE_ID}/origin
Retrieve a rule's related origin
retrieveRuleOrigin 5 params → 200
GET
/rules/{RULE_ID}/revisions
List a rule's revisions
listRuleRevisions 7 params → 200
GET
/rules/{RULE_ID}/rule_component_notes
List the notes for a rule's components
listRulesComponentsNotes 10 params → 200
GET
/rules/{RULE_ID}/notes
List a rule's notes
listRuleNotes 10 params → 200
POST
/rules/{RULE_ID}/notes
Create a note for a rule
createNoteRule 5 params body → 201
GET
/properties/{propertyId}/rules
List Event Forwarding Rules
listEventForwardingRules 5 params → 200
POST
/properties/{propertyId}/rules
Create an Event Forwarding Rule
createEventForwardingRule 1 param body → 201422
GET
/rules/{ruleId}
Retrieve an Event Forwarding Rule
getEventForwardingRule 1 param → 200404
PATCH
/rules/{ruleId}
Update an Event Forwarding Rule
updateEventForwardingRule 1 param body → 200404422
DELETE
/rules/{ruleId}
Delete an Event Forwarding Rule
deleteEventForwardingRule 1 param → 204404
GET
/rules/{ruleId}/libraries
List Libraries for a Rule
listLibrariesForRule 1 param → 200
GET
/rules/{ruleId}/revisions
List Revisions for a Rule
listRevisionsForRule 1 param → 200
GET
/rules/{ruleId}/origin
Get the Origin for a Rule
getOriginForRule 1 param → 200
GET
/rules/{ruleId}/property
Get the Property for a Rule
getPropertyForRule 1 param → 200

Schemas 71

The contract defines 71 schemas that model the data the API accepts and returns. The most detailed are PropertyAttributes (12 properties), ruleComponentsAttributes (9 properties), LibraryAttributes (5 properties), PropertyResource (5 properties). Each schema is shown below with its type and property counts.

RuleSingleResponse
object
1 property
rulesCreateAttributes
relatedProperty
object
1 property
notesLookupResponse
ruleComponentsAttributes
object
9 properties
notesCreatePayload
Relationship
object
2 properties
notesListResponse
dataUpdateWithMeta
object
1 property 1 required
rulesUpdateResponse
rulesListResponse
metaList
object
1 property
dataCreateWithRelationships
object
1 property 1 required
basicResourceProperties
object
2 properties
rulesPropertyLookupResponse
relatedUpdatedWithExtensionPackage
object
1 property
dataLookup
object
1 property
relatedRuleComponents
object
1 property
PropertyResource
object
5 properties
RuleResource
object
4 properties
ruleComponentsListResponse
rulesRevisionsListResponse
RuleUpdateRequest
object
1 property 1 required
ruleComponentsLookupResponse
rulesCreateResponse
LibraryListResponse
object
2 properties
relatedLibraries
object
1 property
propertiesLookupResponse
ruleComponentsCreatePayload
rulesNotesListResponse
rulesRuleComponentsListResponse
rulesUpdatePayload
ruleComponentsCreateAttributes
relatedCallbacks
object
1 property
LibraryResource
object
5 properties
rulesNotesCreateResponse
relatedExtension
object
1 property
rulesLibrariesListResponse
dataList
object
1 property
relatedRules
object
1 property
rulesCreatePayload
RuleListResponse
object
2 properties
LibraryAttributes
object
5 properties
relatedNotes
object
1 property
notesAttributes
object
1 property 1 required
dataCreate
object
1 property 1 required
propertiesEntity
relatedDataElements
object
1 property
RuleCreateRequest
object
1 property 1 required
relatedUpdatedWithExtension
object
1 property
relatedResource
object
1 property
relatedRevisions
object
1 property
ruleComponentsCreateResponse
PaginationMeta
object
1 property
rulesAttributes
object
2 properties
relatedEnvironments
object
1 property
relatedCompany
object
1 property
ErrorResponse
object
1 property
rulesLookupResponse
relatedOrigin
object
1 property
notesEntity
librariesListResponse
relatedHosts
object
1 property
rulesEntity
PropertySingleResponse
object
1 property
rulesNotesCreatePayload
ruleComponentsRelationships
object
2 properties 1 required
relatedExtensions
object
1 property
ruleComponentsEntity
rulesOriginLookupResponse
PropertyAttributes
object
12 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

adobe-launch-rules-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 Rules 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.