HumDay

Automate Apple App Store Connect

HumDay reads Apple App Store Connect’s own published API description and derives 251 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

Automate Apple App Store Connect

What HumDay can do in Apple App Store Connect

103 documented operations change something in Apple App Store Connect. The 74 most useful are listed here.

  • DELETEDelete id/v1/users/{id}
  • PATCHUpdate id/v1/users/{id}
  • POSTUpdate devices/v1/devices
  • POSTUpdate profiles/v1/profiles
  • POSTUpdate bundleIds/v1/bundleIds
  • POSTUpdate betaGroups/v1/betaGroups
  • POSTUpdate appPreviews/v1/appPreviews
  • POSTUpdate betaTesters/v1/betaTesters
  • POSTUpdate appPreOrders/v1/appPreOrders
  • POSTUpdate certificates/v1/certificates
  • POSTUpdate appPreviewSets/v1/appPreviewSets
  • POSTUpdate appScreenshots/v1/appScreenshots
  • POSTUpdate userInvitations/v1/userInvitations
  • POSTUpdate appStoreVersions/v1/appStoreVersions
  • POSTUpdate idfaDeclarations/v1/idfaDeclarations
  • POSTUpdate appScreenshotSets/v1/appScreenshotSets
  • POSTUpdate routingAppCoverages/v1/routingAppCoverages
  • POSTUpdate appInfoLocalizations/v1/appInfoLocalizations
  • POSTUpdate betaAppLocalizations/v1/betaAppLocalizations
  • POSTUpdate bundleIdCapabilities/v1/bundleIdCapabilities
  • POSTUpdate appStoreReviewDetails/v1/appStoreReviewDetails
  • POSTUpdate betaTesterInvitations/v1/betaTesterInvitations
  • POSTUpdate betaBuildLocalizations/v1/betaBuildLocalizations
  • POSTUpdate buildBetaNotifications/v1/buildBetaNotifications
  • POSTUpdate betaAppReviewSubmissions/v1/betaAppReviewSubmissions
  • POSTUpdate endUserLicenseAgreements/v1/endUserLicenseAgreements
  • POSTUpdate appStoreReviewAttachments/v1/appStoreReviewAttachments
  • POSTUpdate appStoreVersionSubmissions/v1/appStoreVersionSubmissions
  • POSTUpdate appStoreVersionLocalizations/v1/appStoreVersionLocalizations
  • POSTUpdate appStoreVersionPhasedReleases/v1/appStoreVersionPhasedReleases
  • PATCHUpdate id/v1/apps/{id}
  • PATCHUpdate id/v1/builds/{id}
  • PATCHUpdate id/v1/devices/{id}
  • PATCHUpdate id/v1/appInfos/{id}
  • DELETEDelete id/v1/profiles/{id}
  • DELETEDelete id/v1/bundleIds/{id}
  • PATCHUpdate id/v1/bundleIds/{id}
  • DELETEDelete id/v1/betaGroups/{id}
  • PATCHUpdate id/v1/betaGroups/{id}
  • DELETEDelete id/v1/appPreviews/{id}
  • PATCHUpdate id/v1/appPreviews/{id}
  • DELETEDelete id/v1/betaTesters/{id}
  • DELETEDelete visibleApps/v1/users/{id}/relationships/visibleApps
  • PATCHUpdate visibleApps/v1/users/{id}/relationships/visibleApps
  • POSTUpdate visibleApps/v1/users/{id}/relationships/visibleApps
  • DELETEDelete id/v1/appPreOrders/{id}
  • PATCHUpdate id/v1/appPreOrders/{id}
  • DELETEDelete id/v1/certificates/{id}
  • DELETEDelete id/v1/appPreviewSets/{id}
  • DELETEDelete id/v1/appScreenshots/{id}
  • PATCHUpdate id/v1/appScreenshots/{id}
  • DELETEDelete id/v1/userInvitations/{id}
  • DELETEDelete id/v1/appStoreVersions/{id}
  • PATCHUpdate id/v1/appStoreVersions/{id}
  • PATCHUpdate id/v1/buildBetaDetails/{id}
  • DELETEDelete id/v1/idfaDeclarations/{id}
  • PATCHUpdate id/v1/idfaDeclarations/{id}
  • DELETEDelete id/v1/appScreenshotSets/{id}
  • DELETEDelete id/v1/routingAppCoverages/{id}
  • PATCHUpdate id/v1/routingAppCoverages/{id}
  • DELETEDelete id/v1/appInfoLocalizations/{id}
  • PATCHUpdate id/v1/appInfoLocalizations/{id}
  • DELETEDelete id/v1/betaAppLocalizations/{id}
  • PATCHUpdate id/v1/betaAppLocalizations/{id}
  • PATCHUpdate id/v1/betaAppReviewDetails/{id}
  • DELETEDelete id/v1/bundleIdCapabilities/{id}
  • PATCHUpdate id/v1/bundleIdCapabilities/{id}
  • PATCHUpdate id/v1/ageRatingDeclarations/{id}
  • PATCHUpdate id/v1/appStoreReviewDetails/{id}
  • PATCHUpdate id/v1/betaLicenseAgreements/{id}
  • DELETEDelete id/v1/betaBuildLocalizations/{id}
  • PATCHUpdate id/v1/betaBuildLocalizations/{id}
  • DELETEDelete id/v1/endUserLicenseAgreements/{id}
  • PATCHUpdate id/v1/endUserLicenseAgreements/{id}

What HumDay can read from Apple App Store Connect

These are the operations a schedule or a trigger can watch.

  • GETRead users/v1/users
  • GETRead id/v1/users/{id}
  • GETRead apps/v1/apps
  • GETRead builds/v1/builds
  • GETRead devices/v1/devices
  • GETRead profiles/v1/profiles
  • GETRead bundleIds/v1/bundleIds
  • GETRead betaGroups/v1/betaGroups
  • GETRead betaTesters/v1/betaTesters
  • GETRead territories/v1/territories
  • GETRead certificates/v1/certificates
  • GETRead salesReports/v1/salesReports
  • GETRead appCategories/v1/appCategories
  • GETRead appPriceTiers/v1/appPriceTiers
  • GETRead appPricePoints/v1/appPricePoints
  • GETRead financeReports/v1/financeReports
  • GETRead userInvitations/v1/userInvitations
  • GETRead buildBetaDetails/v1/buildBetaDetails
  • GETRead visibleApps/v1/users/{id}/visibleApps
  • GETRead preReleaseVersions/v1/preReleaseVersions
  • GETRead betaAppLocalizations/v1/betaAppLocalizations
  • GETRead betaAppReviewDetails/v1/betaAppReviewDetails
  • GETRead betaLicenseAgreements/v1/betaLicenseAgreements
  • GETRead betaBuildLocalizations/v1/betaBuildLocalizations
  • GETRead betaAppReviewSubmissions/v1/betaAppReviewSubmissions
  • GETRead appEncryptionDeclarations/v1/appEncryptionDeclarations

How automating Apple App Store Connect works

  1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
  2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
  3. See it proven. The program runs and shows you the result before it is allowed near your live Apple App Store Connect account.
  4. Grant access, then go live. You approve the specific Apple App Store Connect operations it may use — and only those.

Automate Apple App Store Connect with these

Categories

Questions about Apple App Store Connect automation

Can HumDay connect to Apple App Store Connect?
Yes. HumDay reads Apple App Store Connect's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 251 operations are documented.
Do I need to write code to automate Apple App Store Connect?
No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Apple App Store Connect account.
What can HumDay do in Apple App Store Connect?
103 of the 251 documented operations change something in Apple App Store Connect, and 148 read from it. HumDay only ever uses the specific operations your approved contract needs.
Is my Apple App Store Connect account safe?
Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Apple App Store Connect is held behind that approval.

Where this came from

The operations above are read from a published API description for Apple App Store Connect at api.apis.guru/v2/specs/apple.com/app-store-connect/1.4.1/openapi.json. Descriptions are the provider’s own words, not ours. Last published 2021-06-09.