API Support & Billing
Send questions about API keys, billing, endpoint behavior, data coverage, ticker examples, OCC symbols, or contract examples to hello@cutemarkets.com. Include the endpoint, ticker, contract or expiration when relevant, and request timestamp when you are debugging a data issue.
Support scope
What to include so we can answer quickly
CuteMarkets support is most effective when the question includes the concrete market-data object involved: stock snapshot, chain, contract, expiration, quote, trade, aggregate bar, indicator, billing record, or account setup step.
API workflow help
Send the endpoint, request parameters, response shape, and the market-data 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 snapshots, chains, expirations, quotes, trades, aggregates, or indicators for a ticker, include the ticker, date, contract symbol when relevant, and timestamp window.
Onboarding guidance
For first integrations, start with the docs and tell us whether you need stock snapshots, option chains, historical contracts, quote history, aggregate bars, indicators, 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.