Skip to content
Vehicle App Store Vehicle App Store — Developer Docs

Upload process

There are two ways to upload a build: the portal UI and the CI upload API. Both run the same automated validation.

Option A — Portal UI

  1. Open your app in the developer portal.
  2. Drag and drop your release APK onto the upload area.
  3. Validation runs immediately; findings appear inline.
  4. Complete the store listing and submit for review.

Option B — CI upload API

Automate uploads from your CI pipeline using a CI token.

1. Create a CI token

In the portal, create a CI token and copy it once (it is shown only at creation time). Store it as a secret in your CI system — never commit it.

2. Upload from CI

POST the APK as multipart/form-data to the upload endpoint, authenticating with your token:

Terminal window
curl -X POST https://api.autoappstore.com/portal/api/uploads/ci \
  -H "Authorization: Bearer $CI_UPLOAD_TOKEN" \
  -F "apk=@app/build/outputs/apk/release/app-release.apk"

A successful response returns the created version and its validation run:

{
  "version": { "id": "…", "version_code": 2, "version_name": "1.1.0", "status": "draft" },
  "validation_run": { "id": "…", "status": "running" }
}

3. Read the result

Poll the validation endpoint (or wait for the email notification) to see findings, then fix and re-upload as needed. See the API reference for the full request/response shapes.

The CI upload API is part of the management API. It is the only upload path you automate against; the in-vehicle distribution layer is internal to the platform and is not part of the developer API.