Skip to content

List App versions
Stable

Request

Lists all versions of a specific application using the V1 schema, which includes direct file and icon URLs, release date, and file size.

Returns a paginated AppVersionV1 collection for the specified application, with the same filter set as the base version list plus timestamp filters. Unlike the base version endpoint, results include app_file (direct APK download URL), app_icon (icon URL), size_in_mb, and release_date.

About List App Versions (V1)

The V1 version list returns the same logical set of version records as GET .../application/{application_id}/version/ but uses the AppVersionV1 schema, which surfaces additional fields that are absent from the base AppVersion schema: a direct download URL for the APK (app_file), an icon URL (app_icon), the file size in megabytes (size_in_mb), and a release_date timestamp. Use the V1 endpoint when your integration needs to display or verify file-level metadata without making additional requests. Note that release_track and target_sdk_version, present in the base schema, are not returned by AppVersionV1.

Key Query Parameters

version_code — filter by version code string

build_number — filter by build number

is_g_play — true returns versions sourced from the Console Google Play Store

approval_status — filter by AVAILABLE, ACCEPTED, APPROVED, or REJECTED

is_enabled — filter for enabled versions

is_default — filter for the default version

created_on_gt / created_on_lt / updated_on_gt / updated_on_lt — timestamp range filters

ordering — sort by installed_count (ascending) or -installed_count (descending)

Common Use Cases

List versions when your integration needs direct APK download URLs or icon URLs without a separate lookup.

Retrieve size_in_mb to estimate storage requirements before deploying a version to a fleet.

Use timestamp filters for incremental sync Workflows that track newly uploaded or updated versions.

Best Practices

Prefer the V1 endpoint over the base version list when you need app_file, app_icon, or size_in_mb — it avoids redundant per-version detail calls.

Note that release_track and target_sdk_version are not available in the V1 schema; use the base version endpoint if those fields are required.

Filter by approval_status=APPROVED and is_enabled=true to limit results to deployment-ready versions.

Workflow

Call this endpoint with the target application_id and relevant filters.

Use app_file and app_icon URLs directly in your integration for display or download.

Record version_id values for use in install commands or V1 version detail lookups.

Security
esper_cloud_api_apiKey
Path
application_idstring, (uuid)required

A UUID string identifying this application.

enterprise_idstringrequired

A UUID string identifying enterprise.

Query
version_codestring

filter by version code

build_numberstring

filter by build number

is_g_playboolean

filter google play applications

approval_statusstring

filter by approval status

Enum:"AVAILABLE""ACCEPTED""APPROVED""REJECTED"
is_enabledboolean

filter by enabled versions

is_defaultboolean

filter by default versions

created_on_gtstring, (datetime)

filter applications created after a given timestamp

created_on_ltstring, (datetime)

filter applications created before a given timestamp

updated_on_gtstring, (datetime)

filter applications updated after a given timestamp

updated_on_ltstring, (datetime)

filter applications updated before a given timestamp

limitinteger

Number of results to return per page.

offsetinteger

Return results from this index.

Default:0
orderingstring

Order result set by field name.

  • installed_count: order by asc
  • -installed_count: order by desc
cURL
curl -i -X GET \
  'https://api.esper.io/_mock/openapi/v1/enterprise/{enterprise_id}/application/{application_id}/version/?version_code=string&build_number=string&is_g_play=true&approval_status=AVAILABLE&is_enabled=true&is_default=true&created_on_gt=string&created_on_lt=string&updated_on_gt=string&updated_on_lt=string&limit=0&offset=0&ordering=string' \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>'

Responses

successful operation

Bodyapplication/json
countintegerrequired
nextstring or null, (url)
previousstring or null, (url)
resultsArray of objects(Application Version V1)required
Response
{
  "count": 0,
  "next": "string",
  "previous": "string",
  "results": [
    { … }
  ]
}