App configurations and callbacks
These endpoint families sit close to application integration and event subscription workflows. They are not usually the first pages a developer reads, but they matter once your application needs configuration records or webhook-style callbacks around Launch activity.
App configurations
Use app configurations for company-level app setup that Reactor exposes through dedicated configuration resources.
| Attribute | Data type | Description |
|---|---|---|
| list_for_company(company_id) | Array<AppConfiguration> | Lists company app configurations. |
| find(config_id) | AppConfiguration | Fetches a single app configuration. |
| create(company_id:, attributes:) | AppConfiguration | Creates a company app configuration with an attribute hash that mirrors Reactor fields. |
| update(config_id, attributes) | AppConfiguration | Updates an existing app configuration. |
| delete(config_id) | nil | Deletes an app configuration. |
| company(config_id) | Company | Traverses back to the owning company. |
Callbacks
Callbacks are property-scoped and useful when you want Adobe Launch to notify your application about build or workflow events.
| Attribute | Data type | Description |
|---|---|---|
| list_for_property(property_id) | Array<Callback> | Lists callbacks configured for a property. |
| find(callback_id) | Callback | Fetches a single callback resource. |
| create(property_id:, attributes:) | Callback | Creates a callback with attributes such as |
| update(callback_id, attributes) | Callback | Updates an existing callback. |
| delete(callback_id) | nil | Deletes a callback. |
These endpoint families are usually read together because they both sit near application-level integration boundaries rather than content-authoring workflows.