Sign in →
Developer1 min read

Developer — Overview

Where developers integrating with Aforo go after the SDK install. Developer Hub for keys, schemas, and the API simulator; Aforo Discussions for help.

Updated 2026-06-30Suggest edits
Docs Developer Overview

The Developer section in the Aforo console is where your team manages everything they need to integrate: API keys, webhook endpoints, the event simulator, the API key audit trail. The Discussions space is the live channel for asking questions and reading what other operators have shipped. Two pages, both load-bearing once you go past Quick Start.

Who this section is for#

Engineers wiring Aforo into a service, integration consultants doing a discovery week, and DevOps owners auditing API key hygiene. This is operator-facing tooling — your end-customers don't see it. (End-customers get their own developer surface inside your Storefront — see .)

Pages in this section#

What lives where#

Developer tooling is split across a few sections in the console; here's the map so you don't hunt for it:

I want to…SectionPage
Mint or rotate an API keyDeveloperDeveloper Hub → Keys
See raw events arrivingIntelligenceIngestion → Recent Events
Try the public API surfaceReferenceAPI Reference (Scalar)
Test a webhook locallyDeveloperDeveloper Hub → Webhook Tester
Send a synthetic eventDeveloperDeveloper Hub → Event Tester
Read the SDK install stepsSDKsSDKs Overview
Configure outbound notification webhooksOperationsAlerts & Notifications
Ask another operator a questionDeveloperAforo Discussions
PRO TIP
Developer Hub's Event Tester routes to a sandboxed tenant on the backend even when you send the request with a production API key. You can stress-test event ingestion without polluting your billable tenant — see the note on the Event Tester surface.
  • SDKs — language-specific install + middleware references.
  • Reference → API Reference — the Scalar-rendered OpenAPI surface for every public endpoint.
  • Gateways — zero-code metering at the edge.
  • Embed Widgets — drop-in billing UI for your customer's site.
  • Troubleshooting — common-issues and rate-limits articles when something looks wrong.