Skip to content
NeticeStart free

NETICE DOCUMENTATION

App Store Connect access setup for Netice

Reviewed

To connect Apple reporting to Netice, prepare an App Store Connect team API key, its issuer ID and key ID, the private key, and the vendor numbers for the reports you need. Apple requires a team key for Sales and Finance endpoints; an individual API key cannot access them. See Apple’s Sales and Finance API requirements.

Choose the report family first. Daily App Sales reads Sales and Trends reports. Platform Finance reads Apple financial reports. Raw Reports syncs the provider-native families you select. Working daily access alone does not demonstrate complete monthly finance coverage.

1. Create a team key with reporting access

  1. Ask your App Store Connect Account Holder to request API access if it has not been enabled.
  2. As an Account Holder or Admin, open Users and Access → Integrations → App Store Connect API → Team Keys.
  3. Generate a key and choose the least-privileged role that permits the selected reports. For finance reporting, Netice’s setup guidance recommends a Finance-role key; generating the key and using its assigned role are separate permissions.
  4. Record the issuer ID and key ID, and download the private key. Apple provides the private-key download once, so keep it in your approved credential storage.

Apple explains API access and team-key creation and key roles and limitations. Team keys apply across the account’s apps; do not assume that choosing a key name restricts it to one app.

2. Identify the right vendor coverage

Apple source scope for each Netice workflow
Workflow What to prepare
Daily App Sales The vendor number associated with your Sales and Trends reports.
Platform Finance Every relevant vendor number shown under your legal-entity/vendor selector in Apple’s Reports / Payments and Financial Reports area.
Raw Reports Vendor access for the selected families; finance families also require the finance region scope, and Customer Reviews requires app resource IDs.

Apple shows vendor numbers below the legal entity name in Reports and in the top-left selector. Multiple numbers can exist after legal-entity changes or for separate revenue streams. Follow Apple’s vendor-number instructions and compare the selection with the scope you intend Netice to read.

For Platform Finance, Netice accepts multiple vendor numbers separated by commas, spaces, semicolons or new lines. Leave Apple Finance scope at its default all-region detail setting unless you deliberately need a specific region set. The default uses Apple’s Z1 detailed scope; it is not a substitute for including all required vendors.

3. Enter or reuse Apple access in Netice

  1. Create the task for Daily App Sales, Platform Finance or Apple Raw Reports and select Apple as the source where required.
  2. Under Choose Apple App Store access, choose an existing saved connection or Set up new Apple App Store access.
  3. For new access, enter Apple Issuer ID, Apple Key ID and the downloaded key contents in Apple Private Key (PEM). Use the issuer ID and key ID belonging to that same key.
  4. Enter the vendor coverage for the selected workflow. For custom raw finance or reviews, complete the additional scope fields displayed by Netice.
  5. Configure the destination separately, then select the initial reporting window and recurring refresh settings.

A saved Apple connection supplies source access. It does not grant permission to write to BigQuery, Snowflake, Google Cloud Storage or S3. Follow the relevant destination setup after completing Apple access.

4. Check one available reporting window

Start with a recent completed day for Daily App Sales or a published closed fiscal month for Platform Finance. Check both source availability and destination delivery. A successful daily report does not validate finance access, and a successful destination check does not validate Apple’s report permissions.

Diagnose the failing part of setup
Symptom Check
Authentication fails Team versus individual key, matching issuer/key/private-key bundle, and whether Apple has revoked the key.
Daily works; finance does not The key’s finance permissions, finance vendor coverage, selected region and fiscal period.
No report for the requested period Publication timing, eligible activity and Apple’s report retention. Do not interpret a missing file as zero proceeds.
A raw family needs more setup Finance region codes or Customer Reviews app resource IDs, depending on the selected family.
The destination cannot be written The destination connection and target permissions, independently of the Apple key.

Keep the Apple report-family reference alongside the first output review. It explains why daily totals, finance periods and source currencies differ.

Maintain access without rebuilding the pipeline

Use saved connections for recurring tasks. When rotating Apple credentials, replace the complete key bundle and verify the affected report families before retiring the old key. Deleting a saved connection in Netice does not revoke the key at Apple; revoke provider access in App Store Connect when it is no longer required.

Choose a backfill and recurring refresh window