> ## Documentation Index > Fetch the complete documentation index at: https://docs.orbit.devotel.io/llms.txt > Use this file to discover all available pages before exploring further. # Tour the Developer hub > One map of the dashboard's Developer section — what each of its 28 pages is for, which deep-dive guide covers it, the order to set things up in, and which roles see which tile. # Tour the Developer hub The **Developer** section of the dashboard is a hub, not a single tool: it collects every surface you touch while building and operating an integration — minting credentials, trying requests, reading what your code actually sent, and pushing events into your own infrastructure. Each tile on the hub's landing page is one of those surfaces. This page is the map: it tells you what each tile does in one sentence and hands you off to the guide that covers it in depth — nothing is walked through twice here. ## Where the hub lives Open the dashboard and pick **Developer** in the left navigation. The hub's landing page shows one tile per surface, grouped by what stage of an integration it serves, plus four computed cards on top — API calls today, average latency, success rate, and active keys. [Read the overview cards](/guides/developer-overview-page) covers those cards and how to drill from one into diagnostics. The hub is built for the developer-facing roles on your organization: **owner**, **admin**, and **developer** accounts see the Developer entry in the navigation. A **viewer** account does not see the hub itself — a read-only analytics surface is the exception, covered in [Who sees what](#who-sees-what) below. ## The hub map Tiles in the order you reach for them, grouped by what they do. A linked tile has a dedicated guide; follow it for the full walkthrough. ### Credentials and control | Tile | What it is | Deep-dive guide | | ------------------ | ------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **API Keys** | Mint keys, scope them, and lock them down — the tile opens the full console in **Settings → API Keys**. | [IP allowlist per key](/guides/api-key-ip-allowlist) · [Usage limits per key](/guides/api-key-usage-limits) · [Choosing scopes](/guides/api-keys-messaging-ccaas-cdp) | | **API Governance** | Org-wide rate-limit defaults plus per-key overrides, read against live usage. | [API governance console](/guides/developer-api-governance-console) · [Rate limits console](/guides/api-rate-limits-console) | | **API Analytics** | Read-only dashboards for latency, success rate, and per-key attribution — safe to hand to a viewer. | [API analytics dashboards](/guides/api-analytics-reader) | ### Try and inspect | Tile | What it is | Deep-dive guide | | ----------------- | ------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------- | | **API Reference** | The in-product endpoint reference, wired to the developer portal's try-it console. | [Developer portal](/guides/developer-portal) | | **Playground** | Build a request by filling a form, run it, and read the generated curl/SDK snippet. | [API playground](/guides/developer-api-playground) · [First request, end to end](/guides/developer-api-playground-tutorial) | | **Request Logs** | Every API call your workspace makes — full payloads, filters, and a live tail. | [Request Logs console](/guides/api-request-logs-console) | | **Delivery Logs** | Trace one message end to end and carry the carrier rejection reason into a ticket. | [Delivery Logs console](/guides/developer-delivery-logs) | | **GraphQL** | Fetch a contact with its conversations and messages — a tree in one request. | [Query with GraphQL](/guides/graphql-querying) | | **Sandbox** | Run the full flow against test numbers and canned receipts before any carrier spend. | [Sandbox and test mode](/guides/sandbox-test-mode) · [Walkthrough](/guides/sandbox-dashboard-walkthrough) | | **SDks** | Install commands and per-language quickstarts for the official client libraries. | [Integrate with the REST API](/guides/api-integration) | | **SDK demo** | Prove your browser-calling setup works by dialing from a demo softphone. | [Browser softphone demo](/guides/sdk-demo-browser-softphone) | | **MCP** | Hand the Orbit MCP server to your AI assistant so it can call the platform for you. | [MCP handshake](/guides/mcp-server-handshake) · [MCP in Claude / Cursor](/guides/mcp-claude-cursor) | ### Events and delivery | Tile | What it is | Deep-dive guide | | ------------------ | --------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | | **Webhooks** | Manage endpoints, rotate signing secrets, review health, and replay deliveries. | [Operate a webhook endpoint](/guides/webhook-endpoint-operations) | | **Webhook Tester** | Fire a test event at your endpoint and inspect exactly what your server answered. | [Test webhooks with the Webhook Tester](/guides/webhook-tester) | | **Event Sinks** | Stream the whole event taxonomy to one destination you run — Kafka or HTTP batch. | [Configure event sinks](/guides/event-sinks-streaming) · [First sink deployment](/guides/event-sink-first-deployment) | | **Event Sources** | Pull your own Kafka topic into Orbit as inbound events. | [Configure event sources](/guides/event-sources-inbound) | ### Integrate elsewhere | Tile | What it is | Deep-dive guide | | ------------------ | ------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | | **Postman** | Download a collection and environment pre-wired to your base URL and org. | [Postman collections](/guides/postman-collections-recipes) | | **Connectors** | App-definition downloads for Zapier, Make, and n8n. | [Connector downloads](/guides/connectors-download) | | **Connected Apps** | Publish an OAuth app a customer installs into their own org with scoped grants. | [Connected Apps with OAuth](/guides/connected-apps) | | **Marketplace** | Browse and install templates, or submit your own listing for review. | [Browse, install, and publish](/guides/marketplace-browse-install-publish) | ### Channel edges and utilities | Tile | What it is | Deep-dive guide | | -------------------- | ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------- | | **SMPP** | Bind an existing SMPP client to Orbit's SMPP edge for high-throughput SMS. | [Connect via SMPP](/guides/smpp) | | **SMTP** | Send email through the SMTP relay rather than the REST endpoint. | [SMTP relay recipes](/guides/smtp-relay-recipes) | | **Sync** | Shared real-time state — durable documents, maps, and lists over REST and WebSocket. | [Sync end to end](/guides/sync-realtime-state) | | **Network APIs** | Operator-asserted identity and fraud signals (GSMA Open Gateway / CAMARA). | [Network signals before you send](/guides/network-signals-open-gateway) | | **QR Tools** | Generate click-to-chat QR codes for SMS or WhatsApp from the dashboard. | [QR Code Tools](/guides/qr-tools) | | **Video Embed Demo** | Join a video room through the web SDK widget inside the dashboard, then copy the embed snippet. | [Video Room Embed Demo](/guides/developer-video-embed-demo) | ## Suggested order of setup New integrations on the hub go smoothest in this order — each stage feeds the next one: 1. **Keys** — mint a key from the **API Keys** tile (it opens Settings), scope it to the channels you actually call, and name it so rotation is obvious. [Choose and scope API keys](/guides/api-keys-messaging-ccaas-cdp). 2. **Scopes → limits** — set a per-key rate limit and monthly quota in **API Governance** before traffic lands, not after. [API governance console](/guides/developer-api-governance-console). 3. **Sandbox** — run the whole flow against [sandbox and test mode](/guides/sandbox-test-mode) first: magic-number sends, canned receipts, simulated inbound. 4. **First request logs** — send one real request and find it in the [Request Logs console](/guides/api-request-logs-console): confirm the payload and status you expected before building further. 5. **Webhook consumer** — receive inbound events, verify signatures, and dry them against the [Webhook Tester](/guides/webhook-tester). [Write a webhook consumer](/guides/webhook-consumer) walks the full loop. 6. **Event sink** — when per-endpoint webhooks stop scaling, point an [event sink](/guides/event-sinks-streaming) at your Kafka topic or HTTP collector for production fan-out. ## Who sees what The **Developer** entry in the dashboard navigation appears for the **owner**, **admin**, and **developer** roles only — those same three roles gate the hub's server-side routes, so an unprivileged account that deep-links in is turned away rather than seeing stub tiles. Grant or revoke higher roles under [Organization → team management](/guides/organization-team-management) when you need to widen access. The one read-only exception is **API Analytics**: its dashboards and their underlying read endpoints also accept the **viewer** role, so the people who watch your integration's health can see the same numbers from a viewer seat. [API analytics dashboards](/guides/api-analytics-reader) details the four-role gating there. Everything else — minting keys, rotating webhook secrets, governing limits, configuring sinks — stays at developer and above. ## See also * [Developer portal](/guides/developer-portal) — the Developer API the hub's pages are built on: try-it console, usage stats, governance, inbound webhook debug, event sinks, OAuth apps. * [Developer hub overview cards](/guides/developer-overview-page) — the latency and success-rate cards on the hub's landing page. * [Authentication](/authentication) — API key formats, roles, and rotation. * [Integrate with the REST API and webhooks](/guides/api-integration) — the full surface-level integration guide.