Support, partnerships, API access, and privacy requests start here
Use the channels below to report platform issues, discuss partnerships, request shared API access, resolve account issues, or submit privacy-related requests.
Contact Scenarios and Best Channels
We recommend contacting us by issue type to reduce back-and-forth. Use the support channel for page errors, stale data, account issues, or login problems. For API, data partnership, or enterprise access, label your request clearly in the subject line.
- Client support, billing, and account compliance queries: `[email protected]`
- API integration / developer gateway access: use a subject like `API Access - <Company or Name>`
- Lead Systems Architect Direct Route (Telegram): `@Ljbp1008`, optimized for complex technical triage or core partnership alignment.
- Quantitative Research Labs (YouTube): `@gexmonitor`, dedicated to streaming market research, option Greeks lessons, and product tutorials.
What to Include in Your Message
A well-scoped message shortens resolution time significantly. This matters especially for trading-data issues where “the page is broken” or “the data looks wrong” is too vague to reproduce quickly.
- The page path where the issue occurred, such as `/btc/options/analytics?tab=gamma`.
- The affected asset, time window, and the abnormal behavior you observed.
- Screenshots, error copy, or relevant route status codes.
- For API issues, include the request method, params, response headers, and a sample response body.
Response and Escalation Guidance
General support questions are typically answered within 1 to 3 business days. System-wide incidents, access problems, or important integration requests are prioritized, and checking the public status page first is still recommended.
The in-app feedback widget is best for UX feedback, improvement ideas, and page suggestions. Formal support, compliance, and partnership requests should still use the contact channels above.