Skip to main content
The Project Settings API manages the project’s top-level configuration: general settings, the project Secret Key, and per-platform store credentials (App Store shared secret / Connect API keys, Play Store service account key).

​
Key concepts

  • General settings — Project display name and optional proxy URLs (proxy_url for SDK traffic, rtdn_proxy_url for Play Store RTDN callbacks).
  • Secret rotation — POST /v4/project-settings/regenerate-secret is deprecated. It creates a new sk_… key, deletes the project’s oldest Secret Key immediately, and returns the new value. Requests with the deleted key are normally rejected within about an hour — see What happens after you delete a key. Every call rotates again, so never retry it automatically. For rotation without downtime, create a second Secret Key in the dashboard, migrate and verify your consumers, then delete the old key — see How to manage and rotate project keys.
  • Store config — GET / POST /v4/project-settings/stores/{platform} where platform is apple or google. Stripe store config is not exposed via this API. Apple requires the App Store Connect API triplet (connect_key_identifier + connect_private_key + connect_issuer_id) to be sent together; same for the In-App Purchase API triplet (iap_key_identifier + iap_private_key + iap_issuer_id). Submitting only 1–2 of a triplet returns 422.

​
Available endpoints

​
Sensitive fields

Secrets (Apple shared secret, Apple Connect/IAP private keys, Google service account key) are never returned in GET responses. Instead the response includes boolean flags — has_shared_secret, has_connect_private_key, has_iap_private_key, has_service_account_key — that tell you whether the value is set. Each store config also carries enabled, which says whether the platform is switched on for the project at all. Switching a store off (enabled: false) needs a signed-in dashboard user: it works through the MCP server, and with a Secret Key alone it returns 403 control_forbidden. On POST (update), omitting a secret field preserves the existing value. To rotate a secret, send the new value explicitly.

​
Authentication

All v4 endpoints require a Secret Key. Rotating the Secret Key and updating store credentials are privileged operations in the manifest sense, but the token type is the same as for reads. See Authentication.