Skip to main content
YALG helps creators and teams turn workspace knowledge into publishable content across posts, scripts, shorts, carousels, and analytics workflows. The Developer API gives you the same workspace-scoped workflows through a stable public /v1 surface.

Start in 5 minutes

Create an API key, call your account endpoint, and make the first authenticated request.

Authentication

Send the x-api-key header and keep keys in server-side environments only.

Rate limits

Understand quotas, per-minute limits, and response headers.

OpenAPI source

Inspect the live OpenAPI 3.1 document that powers the API reference.

​
Base URL

The production API base URL is:
Public integration endpoints live under /v1.

​
Authentication model

Public API requests are authenticated with named API keys. Each request acts as the user who owns the key, so product resources are automatically scoped to that owner.
API keys are shown once. Store them in a server-side secret manager or environment variable, and never expose them in client-side code.

​
Common integration paths

Build a Knowledge Base

Create notes and voice sources, import spreadsheets, or upload private PDF, PPTX, and TXT files for retrieval.

Manage posts

Create drafts, schedule posts, publish, mark external publication, and manage media.

Run generation jobs

Generate post drafts with automatic retrieval and track generation state.

Render blog articles

Fetch finished blog articles with a Developer API key and render their Markdown in your own site.

Read analytics

Pull dashboard summaries, recent posts, and pending validation items.

​
What is generated automatically?

The API reference is generated from https://api.yalg.ai/openapi.v1-3.1.json, the public OpenAPI 3.1 document served by the YALG backend. The backend validates at startup that documented request bodies and non-empty responses include schemas, so the reference stays aligned with the API surface.