Skip to main content
The Nulix REST API gives you full programmatic control over your knowledge base. Use it to pull articles into your product’s help widget, automate content creation from external systems, build custom search experiences, or integrate Nulix data into your own dashboards and tooling. The API follows standard REST conventions and returns JSON for all responses.

Getting an API Key

Before you can make API requests, generate a personal API key from your workspace settings.
1

Open API Settings

In your Nulix workspace, navigate to Settings > API.
2

Generate a New Key

Click Generate API Key. Give the key a descriptive name (for example, production-app or zapier-integration) so you can identify it later.
3

Copy and Store the Key Securely

Copy the key immediately — Nulix only displays it once. Store it in a secrets manager, an environment variable, or a password manager. Never commit API keys to source control.
Keep your API keys secret and rotate them regularly, especially if you suspect a key has been exposed. You can revoke and regenerate keys at any time from Settings > API.

Authentication

Pass your API key as a Bearer token in the Authorization header on every request:
Requests without a valid key return a 401 Unauthorized response.

Base URL

All API endpoints are relative to the following base URL:

Endpoints

The table below summarises the available endpoints. All endpoints require authentication unless otherwise noted.

Example: List Articles

Request

Response

Example: Create an Article

Use POST /articles to create a new article programmatically. Pass a JSON body with the article’s title, body (Markdown), and category_id.

Request

Response

New articles are created as drafts by default. Publish them from the Nulix editor or by sending a PUT /articles/{id} request with "status": "published".

Example: Search Articles

Use GET /search?q= to run a full-text search across all published articles. This is the same index that powers the in-app search bar.

Request

Response

URL-encode your query string when passing multi-word searches. Most HTTP clients handle this automatically, but be explicit when building URLs manually (for example, use %20 or + to represent spaces).

Rate Limits

To ensure reliable service for all users, the API enforces the following request rate limits: When you exceed your rate limit, the API returns a 429 Too Many Requests response. The response includes a Retry-After header indicating how many seconds to wait before retrying.
Use the API to sync Nulix articles into your app’s in-app help widget. Fetch articles by category, cache them on your end, and display contextually relevant results to users without leaving your product.