Integrations and API tokens

Use API tokens to read published content from your workspace.

What is in Integrations

Open Settings → Integrations. The area has two tabs: Connectors and API Tokens.

  • Connectors is where direct publishing connectors will live. It is marked as coming soon, so it cannot be configured yet.
  • API Tokens is available now. Use it when another system needs to read your published content over HTTP.

Create an API token

  1. Open Settings → Integrations → API Tokens.
  2. Enter a descriptive name, for example the system that will use it.
  3. Choose Generate Token.
  4. Copy the token immediately. It is shown only once and cannot be retrieved later.

Send the token with every request:

Authorization: Bearer YOUR_TOKEN

Available endpoints

Endpoint Returns
GET /api/v1/blog/articles Published articles for the workspace.
GET /api/v1/blog/articles/{slug} A single published article.
GET /api/v1/blog/categories The category tree.
GET /api/v1/blog/sitemap Sitemap data for the published site.

Only published articles are returned. Drafts, articles in review, and trashed articles are excluded.

Revoke a token

  1. Find the token in the Active Tokens list.
  2. Choose revoke and confirm.

Revocation takes effect immediately. Any system still using that token starts receiving errors, so update the integration first if it is in production.

Feeds and sitemap

You do not need a token to read the public site. Narranta publishes a sitemap at /sitemap.xml, a robots file at /robots.txt, and an article feed search at /articles/feeds. These follow the same publishing rules as the public pages.

Security: Treat a token like a password. Do not put it in client-side code, a public repository, or screenshots, and revoke tokens you no longer use.

Next steps

Ready to try it in your workspace?

Start free, or contact support if something in this guide does not match what you see.