Skip to content

Commit 7f7cd78

Browse files
committed
added moved under overview
1 parent 85f3ae5 commit 7f7cd78

1 file changed

Lines changed: 12 additions & 8 deletions

File tree

docs/mini-apps/core-concepts/notifications.mdx

Lines changed: 12 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,18 @@ To send a notification, make a `POST` request to the `url` with the user's notif
1313

1414
You will receive webhook events when users enable or disable notifications for your app. When disabled, the notification token becomes invalid and should no longer be used.
1515

16+
## Client App Behavior
17+
18+
Different client apps handle webhook responses differently:
19+
20+
Farcaster app: Activates notification tokens immediately without waiting for a webhook success response.
21+
22+
Base app: Waits for a successful webhook response before activating tokens.
23+
24+
<Note>
25+
If your webhook processes token saving and sends notifications synchronously before returning a response, tokens may work on Farcaster but fail to activate on Base app.
26+
</Note>
27+
1628

1729
<Panel>
1830
![notification-image-iphone](/images/minikit/notifications-sample.png)
@@ -354,12 +366,4 @@ Sent when a user disables notifications from, e.g., a settings panel in the clie
354366
"event": "notifications_disabled"
355367
}
356368
```
357-
## Client App Behavior
358-
359-
Different client apps handle webhook responses differently:
360-
361-
**Farcaster app**: Does not wait for webhook responses and does not require a success response to activate notification tokens
362-
363-
**Base app**: Waits for the webhook to return a success response before activating the notification token.
364369

365-
This means if your webhook processes token saving and sends notifications synchronously before returning a response, tokens may work on Farcaster but fail to activate on Base app.

0 commit comments

Comments
 (0)