iOS · Arazzo Workflow

iOS Notify TestFlight Testers of a New Build

Version 1.0.0

Find a build, push a TestFlight notification to its testers, and confirm the build's beta state.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub iOSAppleMobileApp StorePush NotificationsIn-App PurchasesSubscriptionAuthenticationWalletsDeveloper PlatformArazzoWorkflows

Provider

ios

Workflows

notify-testers-new-build
Resolve a build, send a beta notification, and read its beta state.
Finds a build by version, sends a TestFlight beta notification to its testers, and reads the build beta detail to confirm state.
3 steps inputs: appId, buildVersion outputs: buildId, internalBuildState, notificationId
1
findBuild
Find the build of the app matching the supplied build number.
2
sendNotification
Trigger a TestFlight beta notification prompting the build's testers to install the update.
3
confirmState
Read the build's beta detail to confirm the internal build state and whether auto-notification is enabled.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: iOS Notify TestFlight Testers of a New Build
  summary: Find a build, push a TestFlight notification to its testers, and confirm the build's beta state.
  description: >-
    Lets a team push a fresh build to its existing TestFlight testers on demand.
    The workflow resolves a build by its build number, triggers a beta
    notification so testers are prompted to install the update, and reads the
    build's beta detail to confirm whether auto-notification is enabled and what
    the current internal build state is. Every step spells out its request inline
    so the flow can be read and executed without opening the underlying App Store
    Connect OpenAPI description. All calls require an App Store Connect JWT
    bearer token.
  version: 1.0.0
  x-realizes-capability-ids:
  - BC-4210
  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
      capability_name: Software Release & Deployment Management
      spec: ios-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: buildbetanotificationsApi
  url: ../openapi/ios-buildbetanotifications-api-openapi.yml
  type: openapi
- name: buildsApi
  url: ../openapi/ios-builds-api-openapi.yml
  type: openapi
workflows:
- workflowId: notify-testers-new-build
  summary: Resolve a build, send a beta notification, and read its beta state.
  description: >-
    Finds a build by version, sends a TestFlight beta notification to its
    testers, and reads the build beta detail to confirm state.
  inputs:
    type: object
    required:
    - appId
    - buildVersion
    properties:
      appId:
        type: string
        description: The id of the app whose build testers should be notified about.
      buildVersion:
        type: string
        description: The build number (CFBundleVersion) of the build to notify on.
  steps:
  - stepId: findBuild
    description: >-
      Find the build of the app matching the supplied build number.
    operationId: builds_getCollection
    parameters:
    - name: filter[app]
      in: query
      value: $inputs.appId
    - name: filter[version]
      in: query
      value: $inputs.buildVersion
    - name: limit
      in: query
      value: 1
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      buildId: $response.body#/data/0/id
  - stepId: sendNotification
    description: >-
      Trigger a TestFlight beta notification prompting the build's testers to
      install the update.
    operationId: buildBetaNotifications_createInstance
    requestBody:
      contentType: application/json
      payload:
        data:
          type: buildBetaNotifications
          relationships:
            build:
              data:
                type: builds
                id: $steps.findBuild.outputs.buildId
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      notificationId: $response.body#/data/id
  - stepId: confirmState
    description: >-
      Read the build's beta detail to confirm the internal build state and
      whether auto-notification is enabled.
    operationId: builds_buildBetaDetail_getToOneRelated
    parameters:
    - name: id
      in: path
      value: $steps.findBuild.outputs.buildId
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      internalBuildState: $response.body#/data/attributes/internalBuildState
      autoNotifyEnabled: $response.body#/data/attributes/autoNotifyEnabled
  outputs:
    buildId: $steps.findBuild.outputs.buildId
    notificationId: $steps.sendNotification.outputs.notificationId
    internalBuildState: $steps.confirmState.outputs.internalBuildState

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/ios-notify-testers-new-build-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.