Create app in Appstore using AppStoreConnect API is giving an error.

Hello Apple Developer Team,

I've followed the AppStoreConnect API documentation and created the following:

I've created a API Key in App store > Integrations > Teams key, gave the role as admin.

  1. Created a valid JWT token
  2. When fetching the GET v1/apps, I can see the list of apps.
  3. Also I was able to make GET v1/users as well successfully.
  4. I've the valid bundle Id and capabilities enabled in the developer portal.

Facing an issue while creating an app in App Store using AppStoreConnect API using POST call:

This is my ruby script:

response = api_request(
      method: :post,
      path: "/v1/apps",
      token: token,
      body: {
        data: {
          type: 'apps',
          attributes: {
            name: APP_NAME,
            primaryLocale: LOCALE,
            sku: "SKU#{Time.now.to_i}",
            bundleId: BUNDLE_ID,
            platform: 'IOS'
          }
        }
      }
    )

It gives me below error:

{
  "errors": [
    {
      "id": "09b465fc-316f-47b4-9bc3-9c340cb966aa",
      "status": "403",
      "code": "FORBIDDEN_ERROR",
      "title": "The given operation is not allowed",
      "detail": "The resource 'apps' does not allow 'CREATE'. Allowed operations are: GET_COLLECTION, GET_INSTANCE, UPDATE"
    }
  ]
}

Did anyone was able to successfully create the app in App Store via AppStoreConnect API?

Could you please help me identify the root cause for the above issue and provide some inputs so that I could work on resolving them and move forward in the deployment process.

Appreciate your help in reviewing this.

Thank you, Santosh

Hitting the exact same thing — confirmed this isn't a permissions/scope issue on our end either (Admin-role key, same 403 with "Allowed operations are: GET_COLLECTION, GET_INSTANCE, UPDATE"). Everything else in our app-provisioning pipeline is fully API-key-driven (Bundle IDs, capabilities including updates via PATCH, certificates, profiles) — app creation is the one remaining step that forces us back to an interactive, session-based Apple ID login, since the only working alternative we've found (fastlane's produce tool) goes through a private, non-API-key-compatible endpoint internally.

Filed as FB24429185 if anyone wants to reference it or add their own report against the same gap.

still no endpoint, still forcing manual onboarding for multi-app platforms

Bumping this as it remains a critical blocker for our CI/CD multi-app platform automation. I opened DTS Case ID 22365798 on October 1st to try and get this to the App Store Connect API team, but the ticket has gone completely dark for nearly a month.

Could someone please help flag this DTS ticket internally? We have already documented everything in FB24429393 and FB24429185.