ReactorSDK Documentation

ReactorSDK helps Ruby applications talk to the Adobe Launch Reactor API without hand-rolling OAuth, pagination, or JSON:API parsing. These docs are organized to help a new developer get from installation to a working request quickly, then move into the parts of the SDK they actually need.

Quickstart Authentication Publishing workflows

Guides

If you are starting fresh, read these pages in order: install the gem, configure credentials, run the quickstart, then branch into the endpoint or workflow pages that match your job.

Quickstart

Install the gem, create a client, and prove your Adobe credentials work with a real request.

Authentication & configuration

Set up Adobe credentials safely and understand exactly what the client needs to authenticate.

How the client works

Learn what the gem handles for you: auth, retries, pagination, rate limiting, and typed responses.

Errors & troubleshooting

Understand common failure modes, recovery patterns, and what to check when a request does not work.

Endpoint domains

Once your first authenticated request works, use the pages below to move into the right part of the SDK. Most teams only need one or two of these groups, not the entire API at once.

Companies & properties

Overview page for company discovery, property management, and property-level setup pages.

Rules, data elements & extensions

Overview page for the workflow-resource pages you use to build Launch logic inside a property.

Libraries, builds & revisions

Overview page for packaging, upstream comparison, build execution, revision lookup, and promotion workflows.

Endpoint reference

A complete map of the endpoint groups exposed by `ReactorSDK::Client`.

Suggested path

If you are new to the gem, this reading order usually works best:

Start with Installation and Authentication & configuration.
Run the Quickstart until you can list at least one company or property.
Go to Companies, Properties, or Secrets, environments & hosts if you are discovering org structure or delivery setup.
Go to Rules, Data elements, or Extensions if you are creating or updating Launch logic.
Go to Libraries, Upstream chain, Builds, and Revisions if you are packaging and publishing changes.
Use Errors & troubleshooting whenever a request, build, or workflow step is failing.

Common questions

What is ReactorSDK?

ReactorSDK is a Ruby SDK for the Adobe Launch and Adobe Data Collection Reactor API. It gives you typed Ruby resources, OAuth Server-to-Server authentication, pagination, revision snapshots, and comparison helpers for Launch workflows.

How do I authenticate with ReactorSDK?

Create a ReactorSDK::Client with your Adobe client ID, client secret, and IMS organization ID. The SDK fetches and refreshes the access token automatically.

Can ReactorSDK compare Development against Staging?

Yes. Use Library comparison when you want a library-wide review, or Upstream chain when you want a single rule, data element, or extension compared against its upstream version.

Can ReactorSDK tell me what a changed data element impacts?

Yes. The snapshot-aware data element review helpers expose impacted_rules, which helps reviewers understand which Launch rules should be retested when a data element changes.