> For the complete documentation index, see [llms.txt](https://docs.rtkdata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rtkdata.com/reseller-hub.md). # Reseller Hub - [Reseller Hub: The RTKdata Partner Portal](https://docs.rtkdata.com/reseller-hub/reseller-hub.md): The RTKdata Reseller Hub is the partner portal for selling RTK corrections under your own name: create customers, provision NTRIP licenses, track usage and settle one monthly invoice. - [Reseller Hub Sign In & First Steps](https://docs.rtkdata.com/reseller-hub/getting-started.md): Sign in to the RTKdata Reseller Hub, take the first login tour, and find your way around the sidebar, search, notifications and your profile. - [Reseller Dashboard: KPIs & Quick Actions](https://docs.rtkdata.com/reseller-hub/dashboard.md): The Reseller Hub dashboard: active licenses, trials, renewals, overdue balances, your tier and the live map, with quick actions and a layout you can rearrange yourself. - [Managing Customers in the Reseller Hub](https://docs.rtkdata.com/reseller-hub/customers.md): Create, edit, archive and delete customer records in the RTKdata Reseller Hub, see each customer's licenses, trials, usage and invoice lines, and export the list as CSV. - [NTRIP License Provisioning for Resellers](https://docs.rtkdata.com/reseller-hub/licenses.md): Provision NTRIP licenses in the RTKdata Reseller Hub: data streams, terms, trials, credentials, renewals, upgrades, auto renew and suspensions, plus what blocks new provisioning. - [Reseller Billing: Monthly Collective Invoice](https://docs.rtkdata.com/reseller-hub/billing.md): How RTKdata bills resellers: one bill per month, tier discounts, the upcoming bill, payment status, online payment, PDF and CSV exports, price snapshots and what happens when a bill is overdue. - [Reseller Usage, Live Map & Activity Log](https://docs.rtkdata.com/reseller-hub/usage-and-live-map.md): See which RTKdata licenses are actually connected, watch live RTK sessions and GPS tracks on the map, and read the activity log of license and billing events. - [Reseller Diagnostics & Support Escalation](https://docs.rtkdata.com/reseller-hub/troubleshooting.md): Diagnose a customer's NTRIP problem from the Reseller Hub: live connection signal per license, guided runbooks, and escalation to RTKdata support with the context already attached. - [Reseller API: Provision NTRIP Licenses from Your Shop](https://docs.rtkdata.com/reseller-hub/api.md): Provision RTKdata NTRIP licenses from your own shop: the API area, keys, webhooks, the request log, and which API version fits your integration. - [API v1: Simple Shop Integration](https://docs.rtkdata.com/reseller-hub/api/api-v1.md): API v1 for simple shop integrations: provision a license at checkout, update, renew, suspend, reactivate and cancel it with eight idempotent calls. - [API v2: Partner API Guide for Deeper Integrations](https://docs.rtkdata.com/reseller-hub/api/v2.md): The partner API for resellers: NTRIP licenses, trials, customers, grants and bills, an event feed with signed webhooks, and a sandbox. - [API v2 Error Catalogue: Every Code and What to Do](https://docs.rtkdata.com/reseller-hub/api/v2/errors.md): Every API v2 error code with its HTTP status, what it means, whether it uses up your Idempotency-Key and what to do. - [Customer Portal: Credentials for Your End Customers](https://docs.rtkdata.com/reseller-hub/customer-portal.md): What your end customers see: a magic link sign in, a read only view of their own NTRIP credentials and session history, and the emails the portal sends them, all under your company name. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.rtkdata.com/reseller-hub.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.