OptibitAI Now Has an API: Connect Your Automation Stack to Your Content Engine

Until now, using OptibitAI meant visiting OptibitAI. You logged in, selected a source, chose your artifact type, ran a job, and copied the output into wherever it needed to go. That workflow works. A lot of teams got real value from it. But it has a ceiling: a human has to be present every time content needs to be generated.

That ceiling is gone.

OptibitAI v2.2.0 ships API keys. With a key, any external system, automation platform, agent, or custom script can trigger OptibitAI directly. Your content corpus, personas, integrations, and artifact types are now accessible programmatically. A GitHub release, a Salesforce stage change, a Jira sprint close, a scheduled cron job: any of these can now kick off a full OptibitAI generation run without a human clicking anything.

This post explains what API keys are, how they work, what you can build with them, and how to get started.

What Actually Changes With an API Key

The mental model shift is straightforward: OptibitAI moves from being a tool you visit to infrastructure you call.

Before API keys, the value chain looked like this: something happens (a release ships, a deal advances, a sprint closes), a human notices, a human logs into OptibitAI, a human triggers the generation, a human takes the output somewhere. Four human touchpoints for content that the platform could generate automatically if it knew the trigger had fired.

With API keys, the chain shortens to: something happens, content is generated and delivered. The human touchpoints collapse to zero for routine content operations. What was a workflow that required a person becomes a workflow that runs on its own.

This matters most at scale. If your team ships every two weeks and uses OptibitAI to generate release notes, a blog post, social content, and internal summaries per release, that is roughly eight to twelve manual generation runs per release cycle. Across a year, you are looking at hundreds of manual runs that could be automated. API keys convert that recurring manual work into a pipeline that runs on its own.

How Keys Work: The Proxy Architecture

When you create an API key in OptibitAI, you get a single token. That token is shown to you once, at creation time, and never again. Store it somewhere safe.

When an external system calls OptibitAI using that key, a few things happen that are worth understanding:

Your integration secrets stay inside the platform. OptibitAI already holds your GitHub token, your Jira credentials, your Salesforce connection, your Confluence access. When an external automation calls OptibitAI with an API key, that system never touches those credentials. The API key acts as a proxy. OptibitAI authenticates the incoming request, then uses its own internal credentials to pull data from whatever sources the generation requires. The external caller sees only the API key, nothing else.

Your corpus and personas travel with every request. When a call comes in through the API, it has access to the same corpus, writer personas, and audience personas that you built inside the platform. You do not need to ship your brand guidelines and product knowledge to every external system that triggers a generation. They live in OptibitAI and get applied automatically. Every artifact that comes out of an API call is grounded in the same context as one you triggered manually.

Scoped permissions control what the key can do. You decide at key creation whether it can read from the corpus, write new artifacts, trigger integrations, or some combination. A key for a read-only reporting integration gets different permissions than a key powering a full generation pipeline. Keys can also be scoped to organization-level access or restricted to a specific member's context.

The Use Cases Nobody Has Automated Yet (But Should Have)

The obvious automation is release-triggered GTM content. That one is real and worth doing. But the more interesting use cases are the cross-functional ones: the workflows that span two systems no one thought to connect, that involve a handoff that always gets dropped, that produce value every single time and yet are still done manually at almost every company.

These are the ones worth building first.

Works With Your Stack

API keys work with any platform that can make an HTTP request. These are the integrations teams are building first:

The API follows standard REST conventions with JSON request and response bodies. Authentication uses a bearer token header. If you have called any modern API, the pattern is immediately familiar.

Permissions, Revocation, and Audit Trails

Enterprise teams need more than just access. They need control over who can do what, visibility into what is happening, and the ability to respond quickly when something changes.

• Scoped permissions: Each key is created with explicit read and write permissions. You control whether a key can access the corpus, trigger integrations, generate artifacts, or some combination. A key powering a read-only dashboard has different permissions than one running a full generation pipeline. Least-privilege is the default posture.
• One-time key exposure: The key value is displayed exactly once, at creation. After that, it is not visible in the platform. This prevents key sprawl and forces teams to handle secrets properly from the start. If a key is lost, revoke it and create a new one.
• Instant revocation: Any key can be disabled immediately from the settings panel, with no code changes required on the calling side. If a key is compromised, a contractor leaves, or an integration is decommissioned, the key is gone in one click. The external system stops working immediately.
• Full audit logging: Every API call is logged with a timestamp, the key identifier, the action taken, and the artifact produced. This supports compliance reporting, usage analysis, and incident investigation. You can see exactly what each key was used for and when.
• Proxy architecture: External callers never see the OAuth tokens OptibitAI holds for your integrations. The API key is the only credential that leaves the platform boundary. This keeps your GitHub tokens, Salesforce credentials, and Confluence access inside OptibitAI where they belong.

For organizations with strict data residency requirements, OptibitAI also offers an on-premises Docker deployment option. The API key model works identically in the self-hosted version: same security architecture, same permission controls, same audit trails, with all data remaining inside your infrastructure.

Getting Started in Under Ten Minutes

Creating and using your first API key takes less time than writing release notes by hand.

Step 1: Generate a key. In your OptibitAI settings, navigate to API Keys and click Create Key. Give it a descriptive name (the name of the integration or automation that will use it), set the permission scope, and click Generate. Copy the key immediately. You will not see it again.

Step 2: Make a test call. Verify the key works with a simple request from your terminal:

curl -X POST https://api.optibit.ai/v1/generate \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "source": "github",
    "ref": "v2.2.0",
    "artifact_type": "release_notes",
    "persona": "technical_writer"
  }'

Step 3: Connect your trigger. Add the API call to whatever system fires the event you want to automate. In a no-code automation platform, that is a webhook action step. In n8n, it is an HTTP Request node. In your CI/CD pipeline, it is a curl command in the relevant job. In a Claude agent, it is a tool definition pointing to the endpoint.

Step 4: Review the first automated output. The first few automated runs are worth checking manually to confirm the persona, corpus context, and artifact type are producing the output you expect. Adjust the request parameters as needed. Once the output looks right, the pipeline runs without supervision.

API keys are available to all OptibitAI accounts as of v2.2.0. Organization admins can generate keys from the Settings panel under API Access. Member-level keys can be created by individual users for personal integrations, with organization-level keys available to admins for shared pipelines.

The platform that used to require you to show up has learned to run without you. That is what v2.2.0 ships.

Get started at Optibit.AI or check the API documentation to connect your first automation.