Your own HTTPS endpoint
Set up Webhook
Send selected iPhone messages to an HTTPS endpoint you control.
How this destination works
Fwrd makes a direct HTTPS attempt from the iPhone to this destination when it is active. The destination service still controls final acceptance and delivery.
Before you begin
- An HTTPS endpoint you own or are authorized to use
- A safe test environment that does not expose production data
- Fwrd installed on the iPhone that receives the messages
Set up the destination
6 steps
Prepare an HTTPS endpoint
Use an endpoint designed to receive Fwrd requests. The request schema, authentication options, and example payload will be added after the webhook contract is finalized.
Add Webhook in Fwrd
Open Destinations in Fwrd, choose Add Destination, and select Webhook.
Enter the endpoint securely
Give the destination a clear name and paste the complete HTTPS endpoint URL. Do not include a credential you are not prepared to store on the iPhone.
Endpoint URL ← Your HTTPS receiverSend a test message from Fwrd
Tap Send Test Message and check that it arrives. This proves the credential and the network path. It does not prove the SMS automation, so do not stop here.
Save and keep the destination active
Tap Save Destination and leave Destination Active switched on. An inactive route stays saved on the iPhone but is skipped when messages arrive.
Destination Active ← OnProve it with a real message
Text yourself something that contains nothing private and watch it arrive at the destination. Try it with the iPhone unlocked first, then locked, because locked is the state it will usually be in.
What counts as verified
A saved destination, completed checklist, or successful connection test is setup evidence—not delivery proof. Final verification requires a sanitized incoming SMS on a physical iPhone and the matching result at Webhook, including a locked-device test when that is part of your intended use.