API
Use /api/v1 to manage saved NotiCord workflows from an agent or script. The owner creates the first API key after connecting Discord and Notion.
Create and use a key
- Open API in NotiCordSelect Create key and name it after the agent, script, or automation that will use it.
- Copy the key immediatelyNotiCord shows the full key only once. Store it in the secret store used by that agent or script.
- Send it as a bearer tokenUse the key in the
Authorizationheader for protected/api/v1requests.
Access: every plan includes the API while the subscription or trial has active service. Otherwise protected endpoints return 403 with SUBSCRIPTION_ACCESS_REQUIRED until the owner restores access.
For example, list saved notification rules:
curl https://app.noticord.com/api/v1/notification-rules \
-H "Authorization: Bearer ntc_your_key"
Limits
| Limit | Starter | Standard | Pro |
|---|---|---|---|
| Active API keys | 1 | 2 | 5 |
| Requests/minute | 60 | 120 | 300 |
| Requests/day | 2000 | 10000 | 50000 |
When a key reaches a limit: the API returns 429 with Retry-After and rate-limit headers. After a plan change, if too many keys remain active, only the oldest keys within the new limit can call the API until you revoke extras.
What you can manage
Setup stays in NotiCord: connect Discord and Notion, create or revoke API keys, and link members to Notion identities. The API does not connect accounts or proxy arbitrary Discord and Notion requests.
For a Discord panel button that opens a Create page command using Choose in Discord, include parentPage on that button's open_create_command action. It sets the parent page for everyone using the button. The OpenAPI schema lists the page fields.
What responses include
Keep keys safe
- Revoke keys you no longer use from the app API page. Revoked keys stop working immediately.
- Never put a key in Notion, Discord, source code, or client-side browser code.