TEST: App Store Server Notification Test Event

The TEST notification is a verification event sent to confirm that your server endpoint is reachable and responding correctly to App Store Server Notifications. It does not represent a real transaction or customer action.

When does it fire?

This notification is triggered manually when you request a test notification through the App Store Server API or when configuring your notification URL in App Store Connect. It's used during setup and debugging.

Payload highlights

The test notification follows the same JWS-signed format as real notifications but does not contain meaningful transaction data. It's designed to verify that your endpoint can receive, verify, and process the notification format.

How Yeethook helps

During setup, Yeethook processes test notifications and delivers a confirmation to your channel, letting you verify that the entire pipeline works end-to-end — from Apple to Yeethook to Slack or Discord.

Common use cases

Verify your notification endpoint is configured correctly
Test the end-to-end notification pipeline during setup
Debug notification delivery issues
Confirm Yeethook is receiving and forwarding events

Example payload

The decoded body of Apple's test notification. It is the one type with no signedTransactionInfo at all, so the data object contains nothing but app identifiers and the environment.

{ "notificationType": "TEST", "notificationUUID": "3fc85b09-1d47-4a62-8e05-b7d29a640c1f", "version": "2.0", "signedDate": 1790408322000, "data": { "appAppleId": 1234567890, "bundleId": "com.example.app", "bundleVersion": "142", "environment": "Sandbox" } }

Questions about test

How do I trigger a test notification?

POST to /inApps/v1/notifications/test in the App Store Server API, which returns a testNotificationToken. A follow-up GET on /inApps/v1/notifications/test/{token} reports Apple's own view of the delivery, including the HTTP status your endpoint returned.

Why does the message have no product or price?

Because there is nothing to extract. Yeethook uses a dedicated extractor for TEST that emits only the Environment row, since the payload carries no transaction or renewal JWS to decode. A single-row message is the correct outcome, not a parsing failure.

Does the test go to my Sandbox or Production endpoint?

Whichever environment you called the API in: the sandbox base URL delivers to your sandbox notification URL and the production base URL to the production one. The environment value in the payload confirms which pipeline you just exercised.

test

Learn about the TEST App Store Server Notification V2. A test notification to verify your server endpoint is reachable.