Skip to main content

Overview

Pre-built tooling

ToolsStatus
Pre-built authorization (API Key)
Pre-built authorization UI
Custom authorization UI
End-user authorization guide🚫
Expired credentials detection
ToolsStatus
Pre-built integrations
API unification
2-way sync
Webhooks from Nango on data modifications
Real-time webhooks from 3rd-party API🚫 (time to contribute: <48h)
Proxy requests
ToolsStatus
HTTP request logging
End-to-type type safety
Data runtime validation
OpenTelemetry export
Slack alerts on errors
Integration status API
ToolsStatus
Create or customize use-cases
Pre-configured pagination🚫 (time to contribute: <48h)
Pre-configured rate-limit handling🚫 (time to contribute: <48h)
Per-customer configurations

Pre-built integrations

EndpointDescriptionReadme
POST /categoriesCreate a category in discourse🔗
GET /categoriesList all categories🔗
EndpointDescriptionReadme
POST /topicsCreate a new topic in discourse🔗
PUT /topics/statusUpdate the status of a topic🔗
GET /usersFetches a list of active users from Discourse.🔗
Not seeing the integration you need? Build your own independently.

Access requirements

Pre-RequisitesStatusComment
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
Contribute useful links by editing this page

API gotchas

  • Discourse uses API_KEY authentication mode with Api-Key: apiKey and Api-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
I