Introduction

The NativPost API is a REST interface that lets you drive the same content pipeline that powers the NativPost dashboard. Anything you can do inside the app, from creating a post to launching a campaign, is available programmatically.

What you can build

• Ingest scripts that push scraped ideas, transcripts, or briefs into your workspace as pending content.
• Approval workflows that route posts through your existing review tools before they reach the scheduler.
• Publishing bots that trigger scheduled campaigns from a CRM, calendar, or product-launch event.
• Analytics pipelines that pull performance data into your warehouse alongside the rest of your marketing stack.

Base URL

All requests target a single base URL:

https://app.nativpost.com/api/v1

Every request must include an API key. See Authentication for how to create and rotate keys.

Design principles

• Snake case everywhere. Request bodies and responses use snake_case. The dashboard uses camelCase internally, but the public API normalises both directions.
• Object envelopes. Every resource response includes an object field (for example "object": "content"). List responses wrap results in { "object": "list", "data": [ ... ], "has_more": bool }.
• Stable ids. Prefixed ids like cnt_..., cmp_..., tpl_..., whk_... make it obvious what a value refers to in logs and dashboards.
• Idempotent writes where safe. Creating the same content with the same client-supplied key returns the same resource instead of duplicating.

Availability

The API is included with the Pro, Agency, and Enterprise plans. Free and Starter workspaces can still browse the docs but cannot generate keys until they upgrade. Requests from an inactive subscription return HTTP 402.

Next steps

1. Authenticate and generate your first key.
2. Run the quickstart to create a piece of content in under five minutes.
3. Review the error and rate limit contracts before you go to production.