NOCK Public API and Webhooks Overview
Use NOCK as a standalone ticket system, connect automations, and send signed ticket events to your own systems.
The NOCK Public API lets you build server-to-server workflows around NOCK tickets without requiring Linear or any other project-management integration. You can read project metadata, create tickets, update ticket fields, add customer-visible replies, manage webhook endpoints, and inspect webhook delivery logs.
The default integration strategy is:
- Keep NOCK as the source of truth for feedback tickets.
- Use the Public API to create and update tickets from your own systems.
- Use webhooks to react to NOCK ticket events in Zapier, n8n, Make, GitHub Actions, Jira automation, or custom code.
- Connect Linear only when your team wants Linear issue sync.
Base URL
https://nocknock.cloudAll Public API routes live under /api/v1.
What you can build
Create tickets from any backend
Send bug reports, support escalations, form submissions, or agent-created tasks into NOCK.
Keep external systems in sync
Receive signed events when tickets are created, updated, replied to, or moved between statuses.
Power no-code automation
Connect NOCK to Zapier, n8n, Make, Slack, or your own workflow engine.
Build external adapters
Use API keys and signed webhooks for GitHub Issues, Jira, CRMs, or internal systems.
Give AI agents a stable contract
Use scoped API keys and predictable ticket payloads so agents can read and write NOCK tickets safely.
Connect MCP clients
Connect Codex, Claude Code, and HTTP MCP clients to NOCK with OAuth or Agent Keys.
Manage API keys
Create scoped keys, webhook endpoints, and inspect recent deliveries.
Available resources
| Resource | What it does |
|---|---|
| Projects | Read project IDs, slugs, names, and configured categories available to an API key. |
| Tickets | List tickets, create tickets, read ticket details, update workflow fields, and add customer-visible replies. |
| MCP | Let coding agents read and update NOCK tickets through a hosted MCP endpoint with OAuth or scoped Agent Keys. |
| Webhooks | Create, list, and disable webhook endpoints. |
| Delivery logs | Inspect webhook attempts, failures, retries, and delivered events. |
Native integrations vs external adapters
Linear is the only native project-management integration in NOCK today. GitHub Issues and Jira are not built-in NOCK adapters yet.
Use External Adapters when you want GitHub, Jira, Zapier, n8n, Make, Slack, CRMs, or custom systems to react to NOCK tickets. The adapter can be a no-code workflow, a serverless function, or your own backend.
Event types
| Event | Trigger |
|---|---|
ticket.created | A ticket is created from the widget, Customer Portal, dashboard, or Public API. |
ticket.updated | Ticket content or workflow fields changed. |
ticket.status_changed | A ticket status changed. |
ticket.note.created | A customer-visible reply was created. |
When a status changes, NOCK emits both ticket.updated and ticket.status_changed. Consumers should use x-nock-delivery or the payload id for idempotency.
OpenAPI
The machine-readable OpenAPI contract is available at /openapi.yaml. Use it to generate typed clients or validate automation payloads.
Note
Public API and webhook features are designed around NOCK-native tickets first. GitHub Issues and Jira do not need native NOCK integrations to work: build adapters with API keys, signed webhooks, and a small mapping layer.