Skip to content

List MAD API docs in the API Reference sidebar and link to them from MAD pages - #3718

Open
karansharmasauce wants to merge 1 commit into
mainfrom
docs/mad-api-in-dev-api
Open

karansharmasauce wants to merge 1 commit into
mainfrom
docs/mad-api-in-dev-api

Conversation

@karansharmasauce

Copy link
Copy Markdown
Collaborator

Description

Lists the Mobile App Distribution (MAD) API pages in the API Reference sidebar (/dev/api) and links to them from the MAD docs. The pages stay in docs/app-distribution/developer/, so their URLs don't change.

  • Added a Mobile App Distribution API category to the API Reference sidebar, between Jobs and Performance. It contains API Reference, Legacy API (v1) and API Migration Guide.
  • Removed the Developer category from the App Distribution sidebar, so the pages aren't listed twice. A single API Reference link replaces it.
  • Linked API mentions on six App Distribution pages to the API docs: Notifications, Organization, OIDC Authentication (settings), Service Accounts, Sauce Labs Connection and Fastlane.

Motivation and Context

The API link in the docs top bar opens /dev/api, but MAD wasn't listed there. Thiago Veronese raised this, and we agreed to keep the MAD API docs in the API section next to Builds, Jobs and the other APIs, and to link to them from the MAD documentation. All API docs then sit together in the API section.

Types of Changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation fix (typos, incorrect content, missing content, etc.)

@github-actions

github-actions Bot commented Oct 9, 2026

Copy link
Copy Markdown

Deploy preview ready for 3718!
https://docs.dev.saucelabs.net/pr-preview/pr-3718

## Copying Builds to App Storage

Copying a build to SauceLabs App Storage is opt-in, not automatic. To copy a build, check **Also upload to SauceLabs App Storage** when uploading it, or send `sync_to_saucelabs=1` through the API.
Copying a build to SauceLabs App Storage is opt-in, not automatic. To copy a build, check **Also upload to SauceLabs App Storage** when uploading it, or send `sync_to_saucelabs=1` through the [API](/app-distribution/developer/api-reference#upload-parameters).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Copying a build to SauceLabs App Storage is opt-in, not automatic. To copy a build, check **Also upload to SauceLabs App Storage** when uploading it, or send `sync_to_saucelabs=1` through the [API](/app-distribution/developer/api-reference#upload-parameters).
Copying a build to Sauce Labs App Storage is opt-in, not automatic. To copy a build, check **Also upload to Sauce Labs App Storage** when uploading it, or send `sync_to_saucelabs=1` through the [API](/app-distribution/developer/api-reference#upload-parameters).

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants