Connect voice notes to your webhook
Whim captures the thought. Your server decides what happens next.
You can record and keep voice notes on your iPhone and Apple Watch without a webhook. To deliver audio to your own workflow, connect Whim to a compatible endpoint you control. This guide explains how to connect your receiver, test delivery, and troubleshoot common errors.
1. Choose your destination
Your endpoint needs to accept an HTTP POST with two multipart parts: metadata containing JSON, and audio containing an AAC .m4a recording. Use the webhook contract to build or adapt your receiver.
Whim sends audio and metadata directly to that endpoint. It does not use a Whim-hosted relay. Your receiver can store the Note, send it to your chosen transcription service, or pass it to the next step of your workflow.
Use a public HTTPS URL with a valid certificate, such as https://audio.example.com/receive. Enter the final URL directly: Whim rejects redirects. HTTP is supported for private IPv4 destinations on a trusted local network; use HTTPS for a server reachable away from home.
2. Connect Whim
On your iPhone:
- Open Whim and tap the settings button, then Webhook.
- Enter your Webhook URL, including the endpoint path.
- If your server requires authentication, enter its Bearer token without the
Bearerprefix, and its HMAC secret. These must match your receiver’s configuration. - Add any custom headers your endpoint needs.
- Tap Save, then Test webhook. Save any edits before testing.
Whim stores secret credentials in the platform Keychain. Your webhook configuration synchronizes from iPhone to your paired Apple Watch; let that synchronization finish before testing Watch delivery.
3. Test a real Note
Test webhook sends a bundled, non-sensitive test recording. It uses event: "configuration.test" and does not create a Note in your local history. Your server should validate it and acknowledge its Note ID without adding it to your normal processing queue.
After the test passes, record a short Note and tap Stop. Open previous Notes to check that its status becomes Sent, then check your receiver for the audio. If Whim offers Retry unsent Notes, use it for Notes waiting for setup or a retry.
4. Make the workflow yours
Your server receives the original audio, a title, capture date and duration, source device kind, and identifiers for the Note and its delivery Attempt.
What comes next is up to you. Your workflow can transcribe a thought into a notebook, turn a reminder into a shopping list, or organize the key points for your next meeting. Full transcription, AI processing, and downstream steps need your own setup; Whim does not provide a hosted AI service.
The same Note can arrive from both iPhone and Watch. Deduplicate by Note ID, so your workflow creates one logical item. The webhook contract describes authentication, acknowledgements, and retries.
If something needs attention
Check Settings → Webhook errors in Whim for failed delivery Attempts.
| What you see | What to check |
|---|---|
| Cannot connect | Check the server, endpoint URL, device network, and firewall. On local Wi-Fi, use your computer’s private IP address; 127.0.0.1 points to the iPhone itself. |
| Certificate or redirect error | Enter the final HTTPS URL and use a publicly trusted certificate. |
401 |
Check that the bearer token and HMAC secret match your server. |
404 |
Check the endpoint path and reverse-proxy configuration. |
| Test passes but no Note appears | The configuration test is not a user Note. Record and stop a real Note to check storage. |
| A Note stays Failed | Repair the destination or configuration, then use Whim’s Retry action. |
Keep it yours
Your server controls its own storage, processing, and backups. Whim’s retention, deletion, and reset controls affect device storage; they cannot delete a copy already accepted by your endpoint. Choose a destination you control or trust, and read the privacy policy for the full details.