Quick Start vs Manual Setup

When setting up Yeethook, you choose how to connect to App Store Connect. There are two modes: Quick Start and Manual Setup. You can switch from Manual to Quick Start at any time.

Quick Start

Quick Start is the recommended way to connect. You upload your App Store Connect API key (.p8 file) once, and Yeethook handles the rest.

How it works

1. You create an API key in App Store Connect (Users and Access → Integrations → App Store Connect API).
2. You upload the .p8 file, Key ID, and Issuer ID to Yeethook.
3. Yeethook automatically imports your apps, configures webhooks, and starts listening for events.

What Yeethook uses the API key for

Your .p8 key authenticates Yeethook with Apple's App Store Connect API. It is used for three things:

App Store Server Notifications V2

Yeethook registers a server notification URL for each of your apps. These are the subscription lifecycle events (renewals, refunds, revocations, billing issues, etc.) that Apple sends directly to your server. Without the API key you would need to paste the URL into each app's settings manually.

App Store Connect Webhooks

Yeethook sets up webhooks for operational events like app review status changes, build processing updates, TestFlight submissions, and certificate expiration warnings. These are configured under Users and Access → Integrations → Webhooks in App Store Connect.

Event enrichment

When Yeethook receives a webhook or server notification, it calls the App Store Connect API to fetch additional context before forwarding to Slack. For example, a build-processing event gets enriched with the build number, version string, and processing status. A TestFlight event includes tester details and device info. A subscription event includes the original transaction, product details, and renewal history. This is what turns a bare event into a useful Slack notification.

What you get

• Automatic app import — all your apps are pulled from App Store Connect so you can select which ones to monitor.
• Automatic webhook configuration — both server notifications and App Store Connect webhooks are registered on your behalf. No manual copy-pasting of URLs.
• Enriched Slack notifications — every notification includes extra context pulled from the API: build metadata, tester details, transaction history, screenshots, and more.
• Zero maintenance — if Apple rotates endpoints or changes formats, Yeethook adapts automatically.

Requirements

• An App Store Connect API key with the Admin role.
• The .p8 key file (can only be downloaded once from Apple — keep a backup).

Security

Your .p8 key is encrypted with AES-256-GCM before storage. It is never exposed in the UI and is only used server-side to authenticate with Apple's API.

Manual Setup

Manual Setup lets you configure webhooks yourself directly in App Store Connect. No API key is required.

How it works

1. You enter your app details (name and bundle ID) manually in Yeethook.
2. Yeethook generates a webhook URL and secret for you.
3. You configure webhooks yourself in App Store Connect:
   • App Store Connect Webhooks — go to Users and Access → Integrations → Webhooks, add a new webhook, and paste the URL and secret.
   • App Store Server Notifications V2 — go to your app's settings → App Information → App Store Server Notifications, set the production URL, and select Version 2.

What you get

• No API key required — useful if you don't have permission to create API keys, or prefer not to share credentials.
• Full control — you decide exactly which webhooks are configured and where.

Limitations

• Manual webhook configuration — you must set up both App Store Connect webhooks and server notification URLs yourself for each app.
• Basic Slack notifications — without API access, Yeethook cannot call Apple to fetch additional context. Notifications include the event type and basic payload data but no enriched details like build metadata, tester info, or transaction history.
• Per-app setup — server notification URLs are configured per app, so you repeat the process for every app you add.

Which should I choose?

Our recommendation: use Quick Start unless you have a specific reason not to. It takes about two minutes and gives you the best experience.