Choose support for API errors, account access, billing and export-order problems. Choose sales for custom capacity, dedicated delivery or production terms. The page also lists support@0xarchive.io and enterprise@0xarchive.io if email is easier.
Need support? Talk to sales
For anything else, email support@0xarchive.io
FAQ
Include the venue family/deployment, exact symbol, route or schema, UTC start/end, expected result and actual result. For a failed request include the request ID; for an export include the order ID. Do not send API keys, wallet secrets or card details.
Choose sales and describe the routes, symbols, grain, history window, expected request/message volume, concurrency, destination and production requirements. SLA terms are agreed for named routes and workloads, not implied by a general sales conversation.
Use the developer Quickstart and route reference for integration, Status for service state, and dashboard Billing for self-serve plan management. Use dashboard/exports for file orders. Contact support if the specific problem remains, with the relevant request or order ID.
No. Send the request ID, route, exact symbol, UTC bounds and observed error. For file issues include the order ID. Never send API keys, seed phrases, private keys or full card information.