Skip to documentation
AppLaunchFlow/ Docs

Documentation / Getting started

From a saved design to Fastlane

Update captures and localized copy in your active variant, then render a validated store package.

Configure your client

Create a key in your project’s Developer API tab. Keep it in your CI secret manager. Set a different request ID for every new mutation.

Shell
export ALF_API_URL="https://dashboard.applaunchflow.com/api/v1"
export ALF_API_KEY="YOUR_API_KEY"
export ALF_REQUEST_ID="$(uuidgen)"

curl "$ALF_API_URL/account/usage" \
  --header "Authorization: Bearer $ALF_API_KEY"

The release workflow

  1. Create and save the design in the editor, or use the API’s project, template, layout, transform and localization operations.
  2. Use /assets/upload/signed-url to upload captures to the project, or /assets/overwrite to update existing capture paths. GET /translations with generationIdand language, update the layout’s captures and copy, then POST it back with generationId, language,mobileLayout and tabletLayout. IncludedesktopLayout when preserving an existing desktop design. These changes are saved directly in the editor’s active variant.
  3. GET /formats for supported store locales and dimensions. POST /renders with projectId, format IDs and language codes. It uses the active screenshot variant and returns 202. To target a specific existing variant, include variantIdin both your layout edits and render request.
  4. Poll /renders/ID, or receive signed webhooks. After succeeded, GET /renders/ID/manifest and /renders/ID/download. Verify the ZIP checksum before extraction and pass the generated folders to Fastlane.

Render request

{
  "projectId": "PROJECT_UUID",
  "formats": [
    "ios.phone.6.5",
    "android.phone"
  ],
  "languages": [
    "en",
    "de"
  ],
  "package": "fastlane"
}

Languages must match the saved translation codes on the variant. Missing translations or device layouts, unsupported locales and duplicate store destinations fail before dispatch. Each export queues the saved layouts read when the request is accepted. Assets use normal project storage; no fixed versions or separate asset copies are created.