Support
Need help with CuteMarkets or have a question? We're here to assist you. Reach out to us directly at [email protected].
Support scope
What to include so we can answer quickly
CuteMarkets support is most effective when the question includes the concrete options-data object involved: chain, contract, expiration, quote, trade, aggregate bar, snapshot, billing record, or account setup step.
API workflow help
Send the endpoint, request parameters, response shape, and the options workflow you are building. That makes it easier to separate auth, filtering, pagination, and data-model questions.
Billing and plan questions
For subscription, invoice, VAT, or account questions, include the email address on the account and the plan you are evaluating.
Data coverage checks
If you are validating chains, expirations, quotes, trades, aggregates, or snapshots for a ticker, include the ticker, date, contract symbol, and timestamp window.
Onboarding guidance
For first integrations, start with the docs and tell us whether you need live chains, historical contracts, quote history, aggregate bars, or expiration discovery first.
Support response expectations
For API questions, include a reproducible request whenever possible. For account questions, avoid sending passwords, access tokens, or full payment details. We can usually diagnose endpoint behavior from the path, query parameters, status code, request ID, and a small sanitized response excerpt.
If the issue is time-sensitive, check the status page first and include whether the behavior is affecting a production workflow, a research notebook, or an initial API evaluation.