Get the right answer quickly by starting in the right place and sending details support can act on. Contact GraphOps support from the platform when a question involves a specific organization, plan, API key, usage window, invoice, or limit.
Where to start
| Need | Best place to start |
|---|---|
| Billing, invoices, payment methods, taxes, automatic top-ups, or a pending payment | Billing and credits explains purchases, payment details, and recovery actions. |
| A plan increase made by mistake | Contact GraphOps support within 24 hours with the organization and the time of the increase. |
| Sign-in, verification email, or account security | Secure your account covers sign-in methods, verification, and sessions. |
| Limit increase, credit exhaustion, or usage discrepancy | Contact GraphOps support with the organization and UTC time range. |
| API key exposure or access incident | Rotate or revoke the key first, then contact support with the key label and approximate exposure time. |
| An error from the GraphOps platform or its API | Look up the error code in the error reference, which explains each error and what to do next. |
| Service errors or freshness questions | Start with the service's troubleshooting page, then contact support if the issue persists. |
| General service status | Ask GraphOps support in the platform chat for current incident information. |
Contact support
Open the support chat in the platform. If you are not signed in, you sign in first and the chat opens afterwards, in the organization you are working in.
Get support(opens in a new tab)In the platform, you can also choose Help → Get support in the sidebar, or Get support at the bottom of any dialog. Support sees which page or dialog you asked from, so you don't need to describe where you are.
- If chat is still initializing, keep the platform page open and try Get support again once it is ready. Repeated reloads or organization switches can temporarily limit new chat initialization; wait before trying again.
- If you edit a question while waiting for an answer, keep the revised question in the same conversation so support can review it when an automatic answer is withheld.
- When a previous conversation is resolved, you can start another in the same signed-in session. Organization access is checked again for the new conversation.
- You can sign out even if the chat widget stops working. Sign-out revokes its access before ending your session.
Help outside the Platform
Website chat and other GraphOps public support channels can help with documentation, services, general pricing and supported networks. They cannot inspect your organization's account, credits, usage or API keys, even if you use the same email address. For account-specific help, sign in to the Platform and open support for the relevant organization. You can ask for a person in the channel where you started.
What to include
Give support enough context to identify the organization and time window without exposing secrets. A request like this one can usually be investigated without a follow-up question:
Reference example
Organization: acme-productionName or IDProduct: RPCThe affected serviceAPI key label: production-indexerThe label, not the keyTime: 2026-10-21 14:00-14:20 UTCUTC rangeLocal time zone: Europe/LondonEndpoint: /v1/evm/1Or Endpoint Alias, Deployment CID, packageRequest ID: <REQUEST_ID>When availableError: 429 Too Many RequestsStatus and safe error bodyExpected: steady 20 requests per secondWhat you expected insteadIf a request failed, include the error code from the response. For billing questions, add the
Stripe receipt or invoice reference. Attach a screenshot when it
helps, with secrets redacted.
Never send plaintext API keys, passwords, verification codes, session credentials, URLs that contain a key, or payment card details. If a key was exposed, rotate it before opening the support request.
What support can see
To answer questions about your account, support can look up the organization you have selected: its services, Endpoint Aliases, Managed Subgraphs, API key labels, billing, credits, and usage. Support sees only what your role lets you see. For example, member and invitation lists require an Owner. Support never sees plaintext API keys or payment details.
Switching organizations, signing out, losing access, or resolving the conversation ends support's access to your earlier account data. Support can explain how to make a change; you make resource and billing changes in the platform.
Support may share a generalized suggestion with the GraphOps team when documentation or a product flow is confusing. Keep credentials and payment details out of support messages.
Share product feedback
Suggest an improvement or tell us what could work better without leaving your current task.
- On a documentation page, choose Provide feedback at the bottom of the article.
- In the platform sidebar, open Help → Provide feedback.
Write your feedback, optionally choose a type, and select Send feedback. For a problem, describe what happened and what you expected. For an improvement, explain what you want to achieve and why it matters. A success message confirms that your feedback was saved; an individual reply or implementation is not guaranteed. Use Get support for urgent issues or account help.
Both forms include the complete page URL, application version when available, and browser details. The platform also includes your account and organization context; expand Included context to check it. Keep API keys, passwords, and personal details out of feedback. Feedback also records your original IP address when available. Feedback records, including that address, are retained indefinitely for product investigation and abuse prevention.
Closing or reloading preserves your draft for that page (and organization in the platform) during the browser session when browser storage is available. If sending fails, use Retry feedback to submit the same response.
Request a network or data
Tell us which network or data you need when GraphOps doesn't serve it yet. Select Request coverage below a network list, on a search that finds no network, package or Subgraph, or where a network doesn't support Managed Subgraphs. The feedback form opens with Request a network or data coverage selected, and with your search filled in when you came from one. You can also choose that type from Provide feedback.
Name the network or data, and describe what you plan to build with it. Requests help us plan new coverage; we can't promise when a network or dataset becomes available.
Next steps
Last updated