OnyxIQ authenticates users through a session cookie set at sign-in. There are no API keys to generate or manage — your session is the credential. This keeps things simple for web users and still works for direct API integrations when you pass the cookie explicitly.Documentation Index
Fetch the complete documentation index at: https://docs.onyxiq.in/llms.txt
Use this file to discover all available pages before exploring further.
Signing in
Go to onyxiq.in/login and sign in with your email address and password. After a successful sign-in, a session cookie is set in your browser automatically. All subsequent requests from the browser include this cookie without any extra steps.Authenticating API requests
Every protected endpoint — includingPOST /api/openclaw/scrape — requires a valid session cookie. In the browser, this happens automatically. For server-side or command-line requests, you need to copy the session cookie from your browser and pass it explicitly.
To find your session cookie:
- Sign in at onyxiq.in/login.
- Open your browser’s developer tools and go to Application → Cookies.
- Look for a cookie named
sb-<project-ref>-auth-tokenon theonyxiq.indomain. - Copy its value and include it in your request’s
Cookieheader.
cURL example
Error responses
401 — Not signed in
If you send a request without a valid session cookie, or if your session has expired, the API returns a401 error.
402 — Insufficient credits
If your account does not have enough credits to complete the requested action, the API returns a402 error. No credits are deducted.
Endpoints that do not require authentication
The contact form endpoint (POST /api/contact) does not require a session. All product endpoints, including OpenClaw, do require authentication.