Skip to main content
For problems connecting an AI assistant, see MCP troubleshooting.

Status codes

Errors in the browser

If your web page calls the API and the browser reports a network or CORS error, but the same request works from cURL, the browser blocked it. The API accepts browser requests only from Itoflow’s own websites, so requests from your site’s front end will fail. Call the API from your server instead and keep the token there. Your code must send an access token in the Authorization header. The Itoflow app’s sign-in cookie isn’t available to other sites, and these docs never send it.

Feature-specific problems

  • Chat: a dropped connection doesn’t stop a research turn. Check the turn’s status before you send the message again.
  • Strategies: a 409 on an edit means someone saved a newer version. Reload it. After a 202 from a run, follow that run instead of starting another.
  • Monitors: check report_scheduling after you enable a schedule. Follow the execution_id you got back; an older completed report doesn’t mean the new one finished.
  • Billing: a positive spending cap needs a paid plan. After a plan change, follow the payment status.
  • Portfolios and brokers: approval, sending to the broker, and the fill are separate steps. Check the trade’s attempts.

Asking for help

Email support@itoflow.ai, or see the help center. Include the method and path, the status code, the time, and the error body. Remove the Authorization header, cookies and personal details first. See API conventions for retries and units.