Adobe Launch · Arazzo Workflow

Adobe Launch Submit, Approve, and Build a Library

Version 1.0.0

Transition an existing library through submit and approve, then compile a build and poll it.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub Data CollectionEdge NetworkEvent ForwardingMarketing TechnologyTag ManagementArazzoWorkflows

Provider

adobe-launch

Workflows

publish-library
Submit then approve a library, build it, and wait for the build to finish.
Applies the submit and approve meta.action transitions to a library, kicks off a build, and polls the build status until it is succeeded or failed.
4 steps inputs: accessToken, apiKey, imsOrgId, libraryId outputs: buildId, buildStatus, libraryId
1
submitLibrary
Transition the library into the submitted state for approval.
2
approveLibrary
Transition the submitted library into the approved state.
3
createBuild
Compile the approved library into a build.
4
pollBuild
Retrieve the build and retry while it is still pending; end the workflow once the build succeeds.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Adobe Launch Submit, Approve, and Build a Library
  summary: Transition an existing library through submit and approve, then compile a build and poll it.
  description: >-
    Adobe Experience Platform Launch (Tags) libraries move through a publishing
    workflow driven by meta.action transitions on the library update endpoint.
    This workflow submits a library for approval, approves it, compiles a build,
    and polls the build until it leaves the pending state, branching on success
    or failure. Each request is written inline using the JSON:API document
    shapes and the documented meta.action transition values these endpoints
    require.
  version: 1.0.0
  x-realizes-capability-ids:
  - BC-4210.10
  x-capability-derivation:
    method: 'deterministic join: sourceDescriptions -> per-tag OpenAPI -> tag/capability edge. No classification at this step.'
    min_confidence: 0.7
    sources:
    - capability_id: BC-4210.10
      capability_name: Continuous Integration Management
      spec: adobe-launch-builds-api-openapi.yml
      confidence: 0.7
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: buildsApi
  url: ../openapi/adobe-launch-builds-api-openapi.yml
  type: openapi
- name: librariesApi
  url: ../openapi/adobe-launch-libraries-api-openapi.yml
  type: openapi
workflows:
- workflowId: publish-library
  summary: Submit then approve a library, build it, and wait for the build to finish.
  description: >-
    Applies the submit and approve meta.action transitions to a library, kicks
    off a build, and polls the build status until it is succeeded or failed.
  inputs:
    type: object
    required:
    - accessToken
    - apiKey
    - imsOrgId
    - libraryId
    properties:
      accessToken:
        type: string
        description: OAuth 2.0 Server-to-Server bearer access token from Adobe Developer Console.
      apiKey:
        type: string
        description: Client ID credential sent as the x-api-key header.
      imsOrgId:
        type: string
        description: Adobe Organization ID sent as the x-gw-ims-org-id header.
      libraryId:
        type: string
        description: Id of the existing library to submit, approve, and build.
  steps:
  - stepId: submitLibrary
    description: Transition the library into the submitted state for approval.
    operationId: updateLibrary
    parameters:
    - name: Authorization
      in: header
      value: "Bearer $inputs.accessToken"
    - name: x-api-key
      in: header
      value: $inputs.apiKey
    - name: x-gw-ims-org-id
      in: header
      value: $inputs.imsOrgId
    - name: libraryId
      in: path
      value: $inputs.libraryId
    requestBody:
      contentType: application/vnd.api+json
      payload:
        data:
          id: $inputs.libraryId
          type: libraries
          meta:
            action: submit
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      libraryId: $response.body#/data/id
  - stepId: approveLibrary
    description: Transition the submitted library into the approved state.
    operationId: updateLibrary
    parameters:
    - name: Authorization
      in: header
      value: "Bearer $inputs.accessToken"
    - name: x-api-key
      in: header
      value: $inputs.apiKey
    - name: x-gw-ims-org-id
      in: header
      value: $inputs.imsOrgId
    - name: libraryId
      in: path
      value: $inputs.libraryId
    requestBody:
      contentType: application/vnd.api+json
      payload:
        data:
          id: $inputs.libraryId
          type: libraries
          meta:
            action: approve
    successCriteria:
    - condition: $statusCode == 200
  - stepId: createBuild
    description: Compile the approved library into a build.
    operationId: createBuild
    parameters:
    - name: Authorization
      in: header
      value: "Bearer $inputs.accessToken"
    - name: x-api-key
      in: header
      value: $inputs.apiKey
    - name: x-gw-ims-org-id
      in: header
      value: $inputs.imsOrgId
    - name: libraryId
      in: path
      value: $inputs.libraryId
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      buildId: $response.body#/data/id
  - stepId: pollBuild
    description: >-
      Retrieve the build and retry while it is still pending; end the workflow
      once the build succeeds.
    operationId: getBuild
    parameters:
    - name: Authorization
      in: header
      value: "Bearer $inputs.accessToken"
    - name: x-api-key
      in: header
      value: $inputs.apiKey
    - name: x-gw-ims-org-id
      in: header
      value: $inputs.imsOrgId
    - name: buildId
      in: path
      value: $steps.createBuild.outputs.buildId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      buildStatus: $response.body#/data/attributes/status
    onSuccess:
    - name: stillBuilding
      type: retry
      retryAfter: 5
      retryLimit: 30
      criteria:
      - context: $response.body
        condition: $.data.attributes.status == "pending"
        type: jsonpath
    - name: buildSucceeded
      type: end
      criteria:
      - context: $response.body
        condition: $.data.attributes.status == "succeeded"
        type: jsonpath
  outputs:
    libraryId: $inputs.libraryId
    buildId: $steps.createBuild.outputs.buildId
    buildStatus: $steps.pollBuild.outputs.buildStatus

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/adobe-launch-publish-library-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.