Using the Makrly Developer API to Automate Content

Create and protect your key

Open Settings, select API, and create a developer key. The full key is shown once. New keys default to read permissions; select the feature scopes your integration needs. Keys can be restricted to one repository. Changing scopes requires a new key.

Send the key from your server in the Authorization header:

curl https://www.makrly.com/api/v1/repos \
  -H "Authorization: Bearer YOUR_MAKRLY_API_KEY"

The request above requires repos:read. Keep the key out of browser code, public repositories, and shared examples.

Access and scopes

Key issuance, writes, and AI generation require an active paid plan, an eligible trial, or lifetime access. Existing authenticated reads and exports remain available after access expires, subject to key expiry, revocation, scopes, repository ownership, and rate limits.

Examples of feature permissions:

• repos:read and commits:read for repository and commit information.
• posts:read and posts:write for social drafts.
• changelog:read and changelog:write for release notes.
• help:read and help:write for Help Center entries and sources.
• ai:generate in addition to the relevant write scope for AI generation.

Rate limits

The limit is 100 requests per fixed 60-second window per key, including on both paid plans. Session requests use a per-user limit. Responses expose X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, and Retry-After. Observe the retry headers when a request is rate limited. If rate-limit storage is unavailable, the API returns 503.

Generation behavior

Commit-based generation saves posts. Custom-text generation returns drafts without saving them. Help Center generation publishes entries that pass the source review. Inbox reply endpoints send real emails, so use them deliberately.

See the Developer API guide and OpenAPI specification for routes, request fields, pagination, and required scopes.