Skip to main content
Every public API request acts as the owner of the API key and resolves an active workspace. This keeps integrations simple and prevents cross-workspace access.

​
Owner-scoped resources

When you create or list resources, YALG uses the authenticated owner from the key:
  • Knowledge Base sources belong to the active workspace
  • posts belong to the key owner
  • generation jobs belong to the key owner
  • scripts, shorts, carousels, b-roll jobs, themes, and analytics are owner scoped
You should not send arbitrary userId or authorId values to public /v1 endpoints.

​
Cross-owner IDs

If a request references a resource ID that does not belong to the key owner, YALG returns a not-found style response instead of exposing another account’s existence.

​
Application routes

The public API is under /v1. Application routes without that prefix are not the public integration surface. Removed source-library routes have no compatibility aliases.