Connect Forked to Mealie
Forked connects to your self-hosted recipe server and helps you discover meals, plan your week, and build shopping lists. Currently, Forked supports Mealie with more servers planned.
What you need
Section titled “What you need”- A running Mealie instance (self-hosted or cloud)
- Your Mealie username (or email) and password, or a Mealie API token
Connect
Section titled “Connect”-
Open Forked and enter your server’s address, for example
recipes.home.lan,192.168.1.50:9000, or a pasted web address. -
Forked checks the server right away and tells you which Mealie version it found.
-
Sign in with your Mealie username and password, or paste an API token instead. Your recipes sync automatically.
Password or API token?
Section titled “Password or API token?”You don’t need an API token. When you sign in with a password, Forked uses it once to create an API token named after your device, such as “Forked (iPhone)” or “Forked (iPad)”, in your Mealie profile and keeps only that token. Your password is never stored, and you can revoke the token in Mealie at any time. Servers that only allow single sign-on use an API token instead.
To use your own token, choose API Token. In your Mealie profile, open API Tokens and create a token. Forked links to that page and has a Paste button.
Which addresses work
Section titled “Which addresses work”A pasted address keeps its port and drops a trailing /api or /mealie path. Mealie must still be available at the host root.
| Address | What Forked does |
|---|---|
| Public hostname | HTTPS only |
Private IP, localhost, or .local name |
Tries HTTPS first, then plain HTTP |
Homelab suffix such as .lab, .lan, or home.arpa |
HTTPS only |
Self-signed or mkcert certificate at home |
Asks whether to trust it |
The port and certificate settings are also under Connection Options.