starred/App-Store-Connect-CLI
1
0
Fork 0
mirror of https://github.com/rudrankriyam/App-Store-Connect-CLI.git synced 2026-04-25 15:45:48 +03:00
Code Issues 2 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #198] Investigate & add App Privacy Details CLI support (public API only) #60

New issue
Closed
opened 2026-02-26 21:33:04 +03:00 by kerem · 2 comments
kerem commented 2026-02-26 21:33:04 +03:00
Owner
Copy link

Originally created by @rudrankriyam on GitHub (Jan 26, 2026).
Original GitHub issue: https://github.com/rudrankriyam/App-Store-Connect-CLI/issues/198

Overview

Add CLI support for App Privacy Details (App Store privacy label: data types collected, tracking, linked/not linked, purposes). This must use public API only; if no public API exists, document the limitation and close.

Docs (App Privacy concept)

These describe the data you must manage, but are not API references:

Discovery (Required)

The App Store Connect API docs (sosumi mirror) do not currently expose an obvious App Privacy endpoint. We must confirm availability via the OpenAPI spec:

Search the spec for terms such as:

  • appPrivacy
  • privacyDetails
  • dataCategories, dataTypes, privacyChoices

If no public endpoints exist, document that in README or a FAQ and close this issue.

Proposed CLI (if API exists)

Top‑level group: asc privacy <subcommand> [flags]

Subcommands (example shape):

  • privacy get --app APP_ID (fetch current privacy details)
  • privacy set --app APP_ID --input ./privacy.json (update full privacy model from JSON)

Because privacy payloads are large/structured, prefer --input JSON file to avoid dozens of flags.

Output

  • JSON (minified) by default
  • --pretty for JSON

Acceptance Criteria

  • Confirm public API support via OpenAPI spec
  • If supported, implement get/set CLI using documented endpoints
  • If not supported, document limitation (no undocumented endpoints)
  • JSON output works for get

Tests

  • CLI validation tests (--app, --input required)
  • HTTP client tests for get/set endpoints (if they exist)

Manual Test Plan (using real apps)

If API exists:

  1. asc apps --paginate → get APP_ID
  2. asc privacy get --app APP_ID → verify JSON
  3. asc privacy set --app APP_ID --input ./privacy.json
  4. Confirm changes in App Store Connect UI (App Privacy section)

Notes

  • Do not use undocumented/private endpoints.
  • If Apple exposes endpoints later, update this issue with exact paths and fields.
Originally created by @rudrankriyam on GitHub (Jan 26, 2026). Original GitHub issue: https://github.com/rudrankriyam/App-Store-Connect-CLI/issues/198 # Overview Add CLI support for **App Privacy Details** (App Store privacy label: data types collected, tracking, linked/not linked, purposes). This must use **public API only**; if no public API exists, document the limitation and close. # Docs (App Privacy concept) These describe the data you must manage, but are **not** API references: - Manage app privacy: https://developer.apple.com/help/app-store-connect/manage-app-information/manage-app-privacy/ - App privacy reference: https://developer.apple.com/help/app-store-connect/reference/app-privacy/ # Discovery (Required) The App Store Connect API docs (sosumi mirror) do **not** currently expose an obvious App Privacy endpoint. We must confirm availability via the OpenAPI spec: - OpenAPI spec (latest): https://raw.githubusercontent.com/EvanBacon/App-Store-Connect-OpenAPI-Spec/main/specs/latest.json Search the spec for terms such as: - `appPrivacy` - `privacyDetails` - `dataCategories`, `dataTypes`, `privacyChoices` If **no public endpoints** exist, document that in README or a FAQ and close this issue. # Proposed CLI (if API exists) Top‑level group: `asc privacy <subcommand> [flags]` Subcommands (example shape): - `privacy get --app APP_ID` (fetch current privacy details) - `privacy set --app APP_ID --input ./privacy.json` (update full privacy model from JSON) Because privacy payloads are large/structured, prefer `--input` JSON file to avoid dozens of flags. # Output - JSON (minified) by default - `--pretty` for JSON # Acceptance Criteria - [ ] Confirm public API support via OpenAPI spec - [ ] If supported, implement get/set CLI using documented endpoints - [ ] If **not supported**, document limitation (no undocumented endpoints) - [ ] JSON output works for get # Tests - CLI validation tests (`--app`, `--input` required) - HTTP client tests for get/set endpoints (if they exist) # Manual Test Plan (using real apps) If API exists: 1) `asc apps --paginate` → get `APP_ID` 2) `asc privacy get --app APP_ID` → verify JSON 3) `asc privacy set --app APP_ID --input ./privacy.json` 4) Confirm changes in App Store Connect UI (App Privacy section) # Notes - Do **not** use undocumented/private endpoints. - If Apple exposes endpoints later, update this issue with exact paths and fields.
kerem closed this issue 2026-02-26 21:33:05 +03:00
kerem commented 2026-02-26 21:33:05 +03:00
Author
Owner
Copy link

@rudrankriyam commented on GitHub (Jan 27, 2026):

Checked the offline OpenAPI spec and a web search: there are no public App Store Connect API endpoints for App Privacy Details (privacy labels). Only related fields are privacy policy/choices URLs. Fastlane does this via internal "iris" endpoints with Apple ID (Spaceship), which we won’t use here. Limitation documented in README; use App Store Connect UI for privacy labels.

<!-- gh-comment-id:3806704184 --> @rudrankriyam commented on GitHub (Jan 27, 2026): Checked the offline OpenAPI spec and a web search: there are no public App Store Connect API endpoints for App Privacy Details (privacy labels). Only related fields are privacy policy/choices URLs. Fastlane does this via internal "iris" endpoints with Apple ID (Spaceship), which we won’t use here. Limitation documented in README; use App Store Connect UI for privacy labels.
kerem commented 2026-02-26 21:33:05 +03:00
Author
Owner
Copy link

@rudrankriyam commented on GitHub (Jan 27, 2026):

Closing: App Privacy Details are not available in the public ASC API.

<!-- gh-comment-id:3806704384 --> @rudrankriyam commented on GitHub (Jan 27, 2026): Closing: App Privacy Details are not available in the public ASC API.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
1.2.6
1.2.5
1.2.4
1.2.3
1.2.2
1.2.1
1.2.0
1.1.1
1.1.0
1.0.1
1.0.0
0.49.1
0.49.0
0.48.1
0.48.0
0.47.1
0.47.0
0.46.2
0.46.1
0.46.0
0.45.4
0.45.3
0.45.2
0.45.1
0.45.0
0.44.2
0.44.1
0.44.0
0.43.0
0.42.0
0.41.4
0.41.3
0.41.2
0.41.1
0.41.0
0.40.1
0.40.0
0.39.1
0.39.0
0.38.3
0.38.2
0.38.1
0.38.0
0.37.3
0.37.2
0.37.1
0.37.0
0.36.3
0.36.2
0.36.1
0.36.0
0.35.3
0.35.2
0.35.1
0.35.0
0.34.1
0.34.0
0.33.2
0.33.1
0.33.0
0.32.0
0.31.3
0.31.2
0.31.1
0.31.0
0.30.0
0.29.3
0.29.2
0.29.1
0.29.0
0.28.14
0.28.13
0.28.12
0.28.11
0.28.10
0.28.9
0.28.8
0.28.7
0.28.6
0.28.5
0.28.4
0.28.3
0.28.2
0.28.1
0.28.0
0.27.0
0.26.4
0.26.3
0.26.2
0.26.1
0.26.0
0.25.4
0.25.3
0.25.1
0.25.0
0.24.3
0.24.2
0.24.1
0.24.0
0.23.5
0.23.4
0.23.3
0.23.2
0.23.1
0.23.0
0.22.1
0.22.0
0.21.0
0.20.2
0.20.1
0.20.0
0.19.3
0.19.2
0.19.1
0.19.0
0.18.2
0.18.1
0.18.0
0.17.0
0.16.0
0.15.0
0.14.0
0.13.0
0.12.4
0.12.3
0.12.2
0.12.1
0.12.0
0.11.0
0.10.2
0.10.1
0.10.0
0.9.0
0.8.1
0.8.0
0.7.0
0.6.0
0.5.0
0.3.1
0.3.0
0.2.0
0.1.6
0.1.5
0.1.4
0.1.3
0.1.2
0.1.1
0.1.0
Labels
Clear labels   
bug

   
bug

   
documentation

   
enhancement

   
pull-request

Mirrored from GitHub Pull Request

No labels
bug
bug
documentation
enhancement
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/App-Store-Connect-CLI#60
No description provided.