- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for notice (0.14 sec)
-
docs/en/docs/advanced/openapi-webhooks.md
!!! info The `app.webhooks` object is actually just an `APIRouter`, the same type you would use when structuring your app with multiple files.
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 2.8K bytes - Viewed (0) -
docs/en/docs/advanced/openapi-callbacks.md
"paid": true } ``` and it would expect a response from that *external API* with a JSON body like: ```JSON { "ok": true } ``` !!! tip Notice how the callback URL used contains the URL received as a query parameter in `callback_url` (`https://www.external.org/events`) and also the invoice `id` from inside of the JSON body (`2expen51ve`). ### Add the callback router
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 7.7K bytes - Viewed (0) -
docs/en/docs/advanced/websockets.md
And to communicate using WebSockets with your backend you would probably use your frontend's utilities. Or you might have a native mobile application that communicates with your WebSocket backend directly, in native code. Or you might have any other way to communicate with the WebSocket endpoint. ---
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Thu May 02 22:37:31 GMT 2024 - 6.2K bytes - Viewed (0)