Newt API

Name: Newt API API
Brand: Newt API
Availability: InStock

✓ Official Vendor SpecMarketingContent Managementbearer5 EndpointsREST

For Agents

Read content, retrieve assets, and submit forms on the Newt headless CMS platform. Single Bearer token spans CDN, content, assets, and form delivery surfaces.

Connect the Newt API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Newt API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Newt API API.

Fetch a paginated list of content items from a Newt model with filter and sort query parameters

Retrieve a single content item by ID for detail-page rendering

Read app metadata including model definitions through GET /space/apps/{appUid}

Download asset files from the {spaceUid}.assets.newt.so subdomain by asset UID and name

GET STARTED

Start building with Newt API API

Explore with Jentic

View OpenAPI Document

Newt is a headless content management platform that exposes four API surfaces from a single Bearer-secured spec — the CDN API for read-only delivery, the Content API for app metadata, the Assets API for media files, and the Form API for form submissions. The five endpoints cover listing and fetching content items, reading app definitions, retrieving asset binaries by name, and submitting form payloads. Each surface lives on a per-space subdomain ({spaceUid}.cdn.newt.so, .api.newt.so, .assets.newt.so, .form.newt.so) so requests are isolated per tenant.

Use Cases

Patterns agents use Newt API API for, with concrete tasks.

★ Headless Site Content Delivery

Marketing teams running a Newt-backed site call GET /{appUid}/{modelUid} for list pages and GET /{appUid}/{modelUid}/{contentId} for detail pages. Combined with GET /space/apps/{appUid} to fetch model definitions at build time, this is enough to render a full content-driven website. The CDN subdomain delivers responses from the edge so live pages stay responsive.

Fetch all published items from the 'blog' model in the 'marketing' app and render a paginated index page

Asset Pipeline for Marketing Pages

Pages that include images or PDFs hosted in Newt fetch them from the {spaceUid}.assets.newt.so subdomain via GET /{assetUid}/{assetName}. The asset server returns the binary directly so the marketing site can stream files without a separate CDN configuration. Pairing the asset endpoint with the content endpoints gives a single CMS pipeline for both copy and media.

Download the asset 'hero-banner.jpg' with assetUid img_2026 from the marketing space

Form Submission for Lead Capture

Marketing landing pages route form submissions to Newt by POSTing to {formUid} on the {spaceUid}.form.newt.so subdomain. Newt stores the response alongside the form definition so the marketing team reviews leads in the same dashboard as content. Adding this endpoint to a static site removes the need for a separate forms-as-a-service vendor.

Submit a contact form with formUid contact-form, name 'Sam', email 'sam@example.com', and message 'demo request'

Agent-Driven CMS Operations

An AI agent uses the Newt API through Jentic to operate across content, assets, and forms in one workflow. The agent might enumerate models in an app, fetch a specific content item, and download its hero image — all on the same Bearer token. Jentic abstracts the four subdomains so the agent treats Newt as one logical API.

For every published blog post, fetch the post content and download its associated hero asset into a manifest

Key Endpoints

5 endpoints — newt is a headless content management platform that exposes four api surfaces from a single bearer-secured spec — the cdn api for read-only delivery, the content api for app metadata, the assets api for media files, and the form api for form submissions.

METHOD

PATH

DESCRIPTION

GET

/{appUid}/{modelUid}

List content items in a model with filter and sort

GET

/{appUid}/{modelUid}/{contentId}

Fetch a single content item by ID

GET

/space/apps/{appUid}

Get app metadata and model definitions

GET

/{assetUid}/{assetName}

Download an asset file from the assets subdomain

POST

/{formUid}

Submit form data to the form subdomain

GET

/{appUid}/{modelUid}

List content items in a model with filter and sort

GET

/{appUid}/{modelUid}/{contentId}

Fetch a single content item by ID

GET

/space/apps/{appUid}

Get app metadata and model definitions

GET

/{assetUid}/{assetName}

Download an asset file from the assets subdomain

POST

/{formUid}

Submit form data to the form subdomain

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Newt Bearer tokens are stored encrypted in the Jentic vault. Jentic injects the Authorization header on every CDN, content, assets, and form call, so the credential never enters the agent's prompt, response, or log output.

Intent-based discovery

Agents search Jentic for intents like 'fetch content', 'download an asset', or 'submit a form', and Jentic returns the matching Newt operation along with the correct subdomain and parameter schema, so the agent doesn't have to know which of the four host bases to target.

Time to first call

Direct integration: half a day to handle the four subdomains, set the spaceUid, wire the Bearer token, and parse content, asset, and form responses separately. Through Jentic: under 20 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Newt CDN API

The newt.so spec covers only the three CDN delivery endpoints, without assets or forms

Choose newt.so when only content delivery is needed and a smaller surface is preferred. Choose this Newt spec when assets and form submission also need to be available on the same Bearer token.

Alternative

Contentful API

Contentful is a larger global headless CMS with delivery, management, and asset APIs

Choose Contentful for multi-region delivery and richer locale handling. Choose Newt when the editorial team is already on Newt and the spec covers content, assets, and forms in one place.

Alternative

Storyblok API

Storyblok bundles a headless CMS with a visual editor and similar delivery endpoints

Choose Storyblok when editors want a visual page builder. Choose Newt when the existing Newt dashboard owns the editorial workflow and forms.

FAQs

Specific to using Newt API API through Jentic.

What authentication does the Newt API use?

Newt uses a Bearer token issued from the Newt dashboard. The same token authenticates the CDN, content, assets, and form endpoints, so an agent only holds one credential. Through Jentic the token is stored in the encrypted vault and injected into the Authorization header automatically.

Can I download an image from Newt with this API?

Yes. GET /{assetUid}/{assetName} on the {spaceUid}.assets.newt.so host returns the asset binary. Combined with the content endpoints, this lets a single agent fetch both the article and its associated hero image in one workflow.

What are the four subdomains in the Newt API?

Newt splits the API across four host subdomains under the {spaceUid} tenant: cdn.newt.so for read content, api.newt.so for content metadata, assets.newt.so for asset files, and form.newt.so for form submissions. Through Jentic the host is selected automatically based on which operation is loaded.

How do I submit a form to Newt through Jentic?

Search Jentic for 'submit a form to newt', load the POST /{formUid} schema, and execute with the formUid and the response payload. Jentic resolves the {spaceUid}.form.newt.so host and injects the Bearer token, so the agent only supplies the form fields.

Can the Newt API create or update content items?

The five endpoints in this spec cover read-only content delivery, asset downloads, and form submission. Creating, updating, or deleting content items is handled through the editing API surface, which is not part of this spec.