Skip to main content

​
No sessions arriving

Almost always an origin mismatch. Open your browser’s network tab and look for a failed request to /v1/ingest. A CORS error means the origin your app is served from is not in Hinto’s allowed list. Add it under Settings, API keys. Remember that http://localhost:3000 and http://127.0.0.1:3000 are different origins, as are different ports.

​
Sessions arriving but not attached to anyone

identify is missing, or it runs before your user object is loaded. Call it after sign-in completes, and again after a user switch. See Identify users.

​
A 401 from the ingest endpoint

The key is wrong, was revoked, or belongs to a different environment. Mint a fresh one under Settings, API keys.

​
A 403 from the ingest endpoint

The key exists but lacks session-ingest permission. Mint a key with the session capture purpose rather than the MCP handoff purpose.