Update Existing Published Applications via API

Update the configuration of an existing Publication. All updatable fields from the POST – Create a Published Application endpoint are supported here, including security mode, build filter, access control, visibility, branding overrides, and legal terms.

Applivery provides two separate APIs for updating Publications, each requiring a different authentication credential.

Choosing the right API

Integrations API

Use this endpoint when updating Publications within the scope of a single app. Authentication uses an App API Token, scoped to the specific App.

To create an App API Token, see Apps API Authentication.

Endpoint

PUT https://api.applivery.io/v1/integrations/distributions/{publishedApplicationId}

Authentication

Authorization: Bearer <your_app_token>

Request format

application/json

Path parameters

Parameters

Identity and Visibility

Security and Access Control

Build Selection Filter

Build Display options

Legal Terms

Branding and App configuration overrides

Example Request

Update a Publication to point to a specific git branch and restrict access to logged-in users in a specific group:

curl 'https://api.applivery.io/v1/integrations/distributions/552ae3cfcb5abfc58d733b81' \
  -X PUT \
  -H 'Authorization: Bearer YOUR_APP_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{
    "slug": "my-app-staging",
    "security": "logged",
    "visibility": "active",
    "filter": {
      "type": "gitBranch",
      "value": "develop"
    },
    "groups": [["qa-team"]],
    "showHistory": true,
    "showDevInfo": true
  }'

Responses

{
  "status": true,
  "data": {
    "id": "string",
    "updatedAt": "string",
    "createdAt": "string",
    "application": "string",
    "applicationInfo": {
      "id": "string",
      "slug": "string",
      "name": "string",
      "picture": "string"
    },
    "slug": "string",
    "filter": {
      "type": "last",
      "value": "string",
      "ios": "string",
      "android": "string",
      "windows": "string",
      "macos": "string",
      "builds": [
        {
          "buildPlatform": "string",
          "id": "string"
        }
      ]
    },
    "security": "public",
    "tags": ["string"],
    "groups": [["string"]],
    "visibility": "active",
    "showHistory": true,
    "showDevInfo": true,
    "distributionUrl": "string",
    "terms": {
      "active": true,
      "text": "string"
    }
  }
}

{
  "status": false,
  "error": {
    "code": 5024,
    "message": "Slug already used"
  }
}

{
  "status": false,
  "error": {
    "code": 4002,
    "message": "No auth token"
  }
}

{
  "status": false,
  "error": {
    "code": 3001,
    "message": "Entity not found"
  }
}

Workspace API

Use this endpoint when updating Publications at the Workspace level using a single credential across multiple Apps.

Authentication uses a Service Account token. To create a Service Account, see Service Accounts.

Endpoint

PUT https://api.applivery.io/v1/organizations/{organizationId}/stores/{storeId}/pubApps/{publishedApplicationId}

Path parameters

Authentication

Authorization: Bearer <your_service_account_token>

Example Request

curl 'https://api.applivery.io/v1/organizations/ORG_ID/stores/STORE_ID/pubApps/PUB_APP_ID' \
  -X PUT \
  -H 'Authorization: Bearer YOUR_SERVICE_ACCOUNT_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{
    "slug": "my-app-release",
    "security": "public",
    "visibility": "active",
    "filter": {
      "type": "last"
    }
  }'

The request body parameters and response schema are identical to the Integrations API.

Managing OTP Access users

OTP (One-Time Password) access is a Publication-level security option that allows you to share Builds securely with external users — freelancers, QA studios, contractors — without requiring them to have an Applivery account or go through your SSO. This is particularly useful for organizations with strict SSO-only Policies that need to share Builds externally without relaxing their global authentication settings.

OTP access is configured per Publication and does not affect any other Publication or the global App Store authentication settings.

How it works

Admin side:

1. Create or update a Publication with OTP access enabled (security: "private" + OTP allowlist configured).

2. Add the email addresses of authorized external users to the OTP allowlist, and configure each user's lifecycle and single-use settings.

User side:

1. The user visits the Publication URL and enters their email address.

2. If their email is on the allowlist, they receive a time-limited OTP via email (valid for 5–10 minutes).

3. They enter the code to verify their identity and gain access to download the App.

4. If single-use is enabled, their email is automatically removed from the allowlist after the first successful download.

Adding OTP Users via API

OTP users are managed separately from the Publication configuration itself, via a dedicated endpoint. This endpoint is called after creating or updating a Publication to add users to its OTP allowlist.

Endpoint

POST https://api.applivery.io/v1/organizations/{organizationSlug}/stores/{storeId}/otp-users

Authentication

Authorization: Bearer <your_service_account_token>

Path parameters

Body parameters

Example Request

curl 'https://api.applivery.io/v1/organizations/my-org-slug/stores/STORE_ID/otp-users' \
  -X POST \
  -H 'Authorization: Bearer YOUR_SERVICE_ACCOUNT_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{
    "email": "[email protected]",
    "temporal": true,
    "singleUse": false
  }'

Responses

{
  "status": true,
  "data": {
    "id": "string",
    "email": "[email protected]",
    "temporal": true,
    "singleUse": false,
    "createdAt": "string"
  }
}

OTP configuration options reference

When to use OTP Access