SDK Developer Community

A company's developer community for its SDK and API: help forums, changelog, showcase, feature requests, DevRel room.

8 categories
36 channels
14 roles
Medium

Choose a server, review what will be created or reused, then confirm. Merge keeps what you have; replace rebuilds the server. Vetox takes a safety backup first either way.

No uses yetNo views yet

Server structure

Channels

WELCOME

quickstart
Install, authenticate, first call. Links to the docs for each SDK.
community-guidelines
Never paste a live key in public. Use #confidential-support for anything with real data.
pick-your-sdk
JavaScript, Python, Go, Java or Mobile SDK, plus Release Pings.
developer-news
Office hours, events and the things that are not a release note.

API HELP

sdk-questions
One thread per question. Tag the SDK, include the version and a minimal snippet with the key removed.
authentication-help
Keys, tokens, scopes and signatures.
webhooks-help
Delivery, retries, signature verification and the event you never received.
rate-limits-and-quotas
429s, backoff and what the limits actually are.
sandbox-and-testing
The sandbox environment, test data and mocking the API in CI.
error-codes
Every error code, what causes it and what to do. Maintained by the team.
confidential-supportHidden from @everyone
Open a ticket for anything that includes a key, a customer or real data.

CHANGELOG AND STATUS

sdk-releases
Every SDK version with its notes. Mentions Release Pings.
api-changelog
API changes by date, breaking ones first.
deprecation-notices
What is going away, when, and what replaces it.
migration-guides
Step-by-step guides for each major version.
api-status
Vetox posts status page updates here.

FEATURE REQUESTS

sdk-feature-requests
One thread per request: the problem first, the proposed feature second. The team tags the state.
docs-issues
Wrong, missing or confusing documentation. Link the page.
public-roadmap
What is planned for the next quarters, maintained by the team.

SHOWCASE

built-with-the-sdk
One thread per project: what it does, which SDK, a link.
community-libraries
Unofficial wrappers, plugins and helpers built by members.
tutorials-and-posts
Blog posts, videos and talks about building with the API.

COMMUNITY

developer-lounge
Everything that is not a question about the API.
partner-loungeHidden from @everyone
Integration partners and the DevRel team.
Builders Lounge
SDK Office Hours
AFK

DEVREL ROOM

devrel-room
Who is answering what, what keeps coming up, what needs a doc.
engineering-escalations
One message per escalation: the thread link, what was tried, what engineering needs to look at.
community-metrics
Weekly numbers: questions, time to first answer, requests shipped.
content-calendar
Posts, videos and office-hours topics by week.
partner-requests
Asks from partners, tracked until they are answered.
devrel-logsHidden from @everyone
Vetox posts moderation, role and ticket logs here.
DevRel Sync

ENGINEERING

sdk-engineeringHidden from @everyone
Engineers only. The fix, the release and the PR.
reproduction-lab
One thread per reported bug: steps, whether it reproduces, which version fixes it.

Roles

SDK Team LeadAdministrator
Developer AdvocateAdministrator
SDK EngineerModerator
Community ModeratorModerator
Partner
Verified Developer
JavaScript SDK
Python SDK
Go SDK
Java SDK
Mobile SDK
Release Pings
Muted

Overview

A server a company runs for the developers building on its SDK or API, staffed by developer advocates with engineers behind them. API Help is the core: #sdk-questions is a forum tagged by language with an Answered tag, and #authentication-help, #webhooks-help, #rate-limits-and-quotas and #sandbox-and-testing take the questions that recur for every API, with #error-codes as a read-only reference maintained by the team and #confidential-support for anything that includes a key or real data. Changelog and Status is read-only in full - #sdk-releases, #api-changelog, #deprecation-notices, #migration-guides and #api-status - with a Release Pings role, so a breaking change is never something a developer discovers in production. Feature Requests is a forum tagged Planned and Shipped as well as by area, next to #docs-issues and a read-only #public-roadmap. Showcase has #built-with-the-sdk as a forum, #community-libraries for unofficial wrappers and #tutorials-and-posts. The DevRel Room is hidden from developers: #devrel-room, #engineering-escalations, #community-metrics, #content-calendar and #partner-requests, with a DevRel Sync voice channel. Engineering is a smaller hidden category for #sdk-engineering and #reproduction-lab, where a reported bug is confirmed before it is answered. A Partner role unlocks #partner-lounge.

When to use it

Your API's community server is a single help channel where a signature question from a Go developer, a rate-limit complaint and a request for a feature already on the roadmap arrive together, and your advocates answer the same three questions every day while breaking changes go unnoticed. This layout gives help a forum tagged by language, gives the changelog a read-only category developers can subscribe to, turns requests into a tagged forum the product team can actually read, and keeps escalation to engineering out of the developers' sight.

What makes it different

#sdk-questions is a forum tagged JavaScript, Python, Go, Java and Mobile, with an Answered tag.
Changelog and Status is fully read-only with a Release Pings role, so breaking changes never surprise production.
#sdk-feature-requests is tagged Planned and Shipped, so the product team's answer is visible on the request.
#engineering-escalations and #reproduction-lab are hidden, so engineering confirms a bug before an advocate answers.
#partner-lounge is unlocked by the Partner role, giving integration partners a channel without a second server.

Recommended Vetox setup

Self-Roles
Post Self-Roles in #pick-your-sdk for JavaScript SDK, Python SDK, Go SDK, Java SDK and Mobile SDK plus Release Pings, so a release note mentions only the developers it affects.
Suggestions
Run Suggestions in #sdk-feature-requests so requests are voted on and a Developer Advocate can mark them Planned or Shipped from the same thread.
Notifications
Use Notifications with your status page's RSS feed posted into #api-status, so an incident lands in the server without an advocate typing it.
Tickets
Put a ticket panel in #confidential-support for questions that include an API key, a customer name or a payload with real data; everything else stays public.
Reminders
Schedule a Reminder in #devrel-room the day before each SDK release so the changelog entry, the migration guide and the Release Pings message are ready together.

Questions

Who can post in the Changelog and Status category?

Developer Advocates and SDK Engineers. It is read-only for everyone else, so a developer can subscribe to it as a feed and trust that every message is an official change. Questions about a release go in #sdk-questions, not under the release.

What is Verified Developer?

A role for developers who have an active API key; an advocate grants it after a quick check. It tells advocates which questions come from someone building in production, and it is the audience for #confidential-support, where a ticket can safely include a key or real data.

How does the Partner role work?

Integration partners - companies building on the SDK with a commercial agreement - get the Partner role, which reveals #partner-lounge and lets the DevRel team track their asks in #partner-requests. It saves running a second server for a dozen people.

Common mistakes

Announcing breaking changes in the general channel, where a developer who was away for a week ships against the old behaviour.
Letting advocates guess at bugs in public; a wrong answer from the company costs more than a slow one confirmed in #reproduction-lab.

Consider instead

Open-Source Project Hub The code is a volunteer-run open-source project rather than a company's product with a DevRel team.

Do you have any doubts?

Our team is there for you

0.0k

Servers

Commands

Users

Languages