APIs & Integrations
Discourse
Overview
Pre-built tooling
Pre-built use cases
Not seeing the use case you need? Build your own independently.
Access requirements
Pre-Requisites | Status | Comment |
---|---|---|
Paid dev account | ❓ | |
Paid test account | ❓ | |
Partnership | ❓ | |
App review | ❓ | |
Security audit | ❓ |
Setup guide
No setup guide yet.
Need help getting started? Get help in the community.
Contribute improvements to the setup guide by editing this page
Useful links
Contribute useful links by editing this page
API gotchas
- Discourse uses API_KEY authentication mode with
Api-Key: apiKey
andApi-Username: API Username
in the request header to access different endpoints. Both keys can be obtained from the admin panel. - Since Nango automatically sets the
Accept: application/json
header, there is no need to include the.json
suffix in API endpoint URLs. For example, instead of sending a request to/categories.json
, you can send it to/categories
, and the JSON response will still be returned.
Contribute API gotchas by editing this page