One form, six topics, one inbox. Pick the topic that matches your question, send it with enough detail to reproduce or price, and the reply comes straight back to the address you used — not from a no-reply sender.
Submissions are rate limited to 5 per hour per IP address. The endpoint replies
{"success": true} once the message is queued for delivery.
The topic you choose becomes the tag on the email subject line, which is how the inbox is triaged. Picking the closest match is the single biggest thing you can do to get a useful first reply instead of a clarifying question.
Plan sizing, quota and rate-limit questions, credit top-ups, invoicing and anything about what a subscription includes.
subject=sales Tagged [Contact Form] Sales & Pricing Volume access, white-label distribution, custom contracts, SLA discussions and procurement paperwork.
subject=enterprise Tagged [Contact Form] Enterprise Solutions A request that will not authenticate, an unexpected status code, a field you cannot place, or an integration that stopped behaving.
subject=technical Tagged [Contact Form] Technical Support Integration partnerships, reseller arrangements and joint distribution proposals.
subject=partnership Tagged [Contact Form] Partnership Documentation that misled you, a response field you wish existed, or a rough edge worth fixing.
subject=feedback Tagged [Contact Form] Feedback Anything that does not fit the five above. It reaches the same inbox; the tag just says Other.
subject=other Tagged [Contact Form] Other The form is a thin client over one JSON endpoint. Knowing the order of the checks tells you what a rejection actually means, and which failures are worth retrying.
Five submissions per hour per client IP, on a sliding window. Over the limit answers 429 with Retry-After: 3600.
The token is verified with Google and scored. Below 0.5 is refused, and a verification error is also refused — the check fails closed, never open.
Field limits are enforced server-side, not just in the browser. A malformed address or a message under ten characters never reaches the inbox.
The email is sent in a background task, so the response does not wait on the mail relay. Your address is set as the Reply-To.
# the request this page sends { "name": "Ada Lovelace", "email": "[email protected]", "company": "Analytical Engines", "subject": "technical", "message": "GET /v1/indicator returns 403 for XAUUSD on H4.", "recaptcha_token": "03AGdBq2..." } # 200 — queued for delivery { "success": true, "message": "Thank you! We'll get back to you within 24 hours." } # 400 — the reCAPTCHA check did not pass { "detail": "reCAPTCHA verification failed. Please try again." } # 429 — over five submissions this hour { "detail": { "error": "Rate limit exceeded", "message": "Too many requests. Maximum 5 requests per 3600 seconds.", "retry_after": 3600 } }
The browser enforces these limits so you find out before you send, but the server enforces them independently. If you post to the endpoint yourself, this is the contract.
| Field | Required | Limits | Notes |
|---|---|---|---|
name | Yes | 1–200 characters | String. Used in the email subject line and greeting. |
email | Yes | Valid address | Validated as an email address, then set as the Reply-To on the message we receive. |
company | Optional | 0–200 characters | Defaults to empty. Omitted from the email when blank. |
subject | Yes | 1–100 characters | One of the six topic values above. An unknown value is passed through unchanged. |
message | Yes | 10–5000 characters | Shorter than ten characters is rejected by validation before anything is sent. |
recaptcha_token | Yes | Non-empty | A reCAPTCHA v3 token for the "contact" action. Supplied by the page, not by you. |
A field that breaks its limit comes back as a validation error naming the field, not as a generic failure — the form surfaces that message rather than replacing it.
Direct email is not rate limited and does not go through reCAPTCHA. Use it when the form refuses you, when you need to attach something, or when you would rather keep the thread in your own mail client.
None of this is a brush-off: the same six checks are what a support reply would ask you to run first, so running them yourself either solves the problem or turns your message into one that can be answered in a single pass.
Parameters, response schemas and defaults are documented per endpoint. Most "which field is that?" questions are answered there in less time than an email round trip.
API referenceThe error pages list the envelope, every status the API returns and what each one means, so you can tell a bad key from a bad parameter from a throttle.
Error handlingPer-plan request quotas and per-minute rate limits are published, along with the headers the API returns so your client can read them instead of guessing.
Rate limitsAuthentication failures, malformed requests, throttling and missing data each have a step-by-step diagnosis path. Running it first also makes your email far easier to answer.
TroubleshootingBefore reporting a fault, check current service health. If something platform-wide is degraded, the status page is the faster source of truth.
Service statusAn integration that worked last week and does not today is often a documented change. The changelog records additions and breaking changes.
ChangelogEndpoint behaviour that does not match the documentation. Authentication and key-scope problems. Unexpected status codes with a reproducible request. Quota and rate-limit accounting that looks wrong. Billing, plan changes and invoices. Gaps or errors in the documentation itself — those get fixed, not just answered.
No investment advice, no position sizing, no view on what an indicator value means for your money. TickAtlas provides market data and computed analytics for software use — it does not provide personalized investment advice, brokerage accounts, trade execution, custody of customer assets or transaction-counterparty services.
We also cannot debug your application for you, restore data we do not have, or make a commitment about a price or limit that is not published.
What the form does with your message, how fast a reply comes back, what the limits are, and which requests belong somewhere other than here.
The form acknowledges every submission with the same commitment the support inbox works to: a reply within 24 hours. Enterprise and procurement threads usually need a second message to gather requirements, so allow for a short exchange rather than one answer.
The endpoint you called, the HTTP status you got back, the exact query string with the key redacted, and the timestamp. Those four things are usually enough to reproduce the problem on the first pass; without them the first reply is only a request for them.
Yes — five submissions per hour, counted per client IP address on a sliding window. Beyond that the endpoint answers 429 with a Retry-After header of 3600 seconds. Email the support address directly if you need to send more than five messages in an hour.
The message field is validated at a minimum of ten characters. A two-word message is almost always an accidental submit, and rejecting it in the browser is faster than a round trip to the server that would reject it anyway.
No. Every submission arrives in the same inbox; the topic sets the tag on the subject line so it can be triaged. Your address is set as the Reply-To, so the answer comes back to you directly rather than from a no-reply sender.
Submissions are protected by reCAPTCHA v3, and verification fails closed — if the check cannot complete, the submission is rejected rather than accepted silently. The page tells you when that happens. If you hit it repeatedly, use the support address directly; it does not go through reCAPTCHA.
Not here. Vulnerability reports have their own address and their own disclosure expectations on the security page, so they are not queued behind sales and support traffic.
Through the GDPR page, which documents the request routes for access, correction, export and erasure. Sending one through this form still works, but the dedicated page tells you what information the request needs.
No. TickAtlas provides market data and computed analytics for software use. It does not provide personalized investment advice, brokerage accounts, trade execution, custody of customer assets or transaction-counterparty services, and support cannot make an exception to that.
If the question is about an endpoint, the reference probably answers it in less time than the reply would take. If it is about scale, price or a contract, the form is the fastest way in — and the answer comes back to your own address.