Let your agent
start signup.
An agent can start a ReelsMeals connection without a browser callback. The user gets one link, creates an account or signs in, and approves access. This uses OAuth device authorization, RFC 8628.
Start the connection
Use the public client ID below. Ask only for the scopes your agent needs. The server returns a private device_code, a user-facing user_code, an approval link, an expiry and a polling interval.
curl https://reelsmeals.com/api/oauth/device \
-H 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'client_id=reelsmeals-agent' \
--data-urlencode 'agent_name=My recipe assistant' \
--data-urlencode 'scope=recipes:read'Show the approval link
Show the user verification_uri_complete and user_code. Keep device_code in the agent's private credential store. Never put it in a URL, chat message or log. A new user signs in with Google or an email code, which creates their account, then checks the matching connection code and approves.
Wait for approval
Wait at least the returned interval before each token request. Continue for authorization_pending. On slow_down, add five seconds to every following wait. Stop for denial, expiry or any other error. The connection expires after 15 minutes.
curl https://reelsmeals.com/api/oauth/token \
-H 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'client_id=reelsmeals-agent' \
--data-urlencode 'grant_type=urn:ietf:params:oauth:grant-type:device_code' \
--data-urlencode 'device_code=DEVICE_CODE_FROM_START'Use the token privately
After approval the token response contains access_token, refresh_token, expires_in and granted scope. Send the access token as a Bearer credential to https://reelsmeals.com/api/mcp. Access tokens last one hour. Refresh tokens last 90 days and rotate on use. Store the new refresh token each time. Revoke through /api/oauth/revoke or ReelsMeals Settings.
This creates an account only after the user signs in. It never bypasses email verification, consent or payment. Public recipe tools are free without this flow. Private cookbook tools still require a paid ReelsMeals plan, checked on every call. A free account can approve a connection now and activate those tools after choosing a plan.
For Claude, Grok and ChatGPT, use their normal connector approval flow instead. Choose your assistant.
Scope names and standard OAuth endpoints are listed in the authorization server metadata.