> ## Documentation Index
> Fetch the complete documentation index at: https://help.verbosec.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrating Verbosec Cloud with Third-Party Tools

> Connect Verbosec Cloud to your existing tools and workflows. Learn about available integrations, webhooks, and the Verbosec API for custom builds.

Verbosec Cloud is built to fit into the tools and workflows you already use. Whether you're connecting a CMS to Nexus AI, automating deployments through Starhost, or building a custom internal tool on top of the Verbosec API, you have several integration options available depending on your use case and technical requirements.

## Integration approaches

<Steps>
  <Step title="REST API">
    The Verbosec REST API is the most flexible integration path. It works with any language or platform that can make HTTP requests, so you can connect Verbosec Cloud to your existing backend, scripts, or third-party automation tools. See the [API Reference](/api-reference/introduction) for full endpoint documentation and request schemas.
  </Step>

  <Step title="Webhooks">
    Webhooks let Verbosec Cloud push event notifications to your own server as soon as an action completes — for example, when an AI content generation job finishes. This removes the need to poll the API for status updates and makes it straightforward to trigger downstream actions in your workflow automatically.
  </Step>

  <Step title="Direct product integrations">
    Verbosec products support direct integrations with popular platforms. Connect Nexus AI to your CMS to publish AI-generated content automatically, or trigger Starhost deployments programmatically via the API whenever your build is ready. Integration options vary by product — check each product's documentation for available connectors.
  </Step>
</Steps>

## Using the REST API for integrations

The Verbosec REST API gives you programmatic access to all Verbosec Cloud services. Authenticate with a Bearer token using your API key (generated from your [Verbosec Cloud dashboard](/verbosec-cloud/account-management)), then call any supported endpoint to trigger generation, manage deployments, retrieve results, or query usage data.

Every API response follows a consistent structure, making it straightforward to build error handling and response parsing that works across multiple Verbosec services. See the [API Reference](/api-reference/introduction) for the full list of endpoints, parameters, and example responses.

## Webhooks

Webhooks give your application real-time notification of events that happen inside Verbosec Cloud, without requiring your code to continuously poll for updates.

**Configuring webhooks**

You can configure webhook endpoints from your Verbosec Cloud dashboard. Navigate to **Settings → Webhooks** and add the HTTPS URL you want Verbosec to send event payloads to.

**Supported events**

| Event                  | Description                                           |
| ---------------------- | ----------------------------------------------------- |
| `content.generated`    | A text generation job has completed                   |
| `image.generated`      | An image generation job has completed                 |
| `voice.generated`      | A voice generation job has completed                  |
| `deployment.published` | A Starhost deployment has been published successfully |

**Example webhook payload**

When an event fires, Verbosec sends a POST request to your endpoint with a JSON payload structured like this:

```json webhook-event.json theme={null}
{
  "event": "content.generated",
  "timestamp": "2025-01-15T10:30:00Z",
  "data": {
    "job_id": "job_abc123",
    "type": "text",
    "status": "completed",
    "output_url": "https://api.verbosec.com/v1/results/job_abc123"
  }
}
```

Use the `output_url` in the payload to fetch the full result from the API once you've received the event notification.

<Note>
  Webhook endpoints must be publicly accessible HTTPS URLs. Verbosec will not deliver events to HTTP endpoints or URLs that require additional authentication headers beyond what's configured in the dashboard.
</Note>

<Tip>
  Use webhooks for asynchronous workflows — trigger downstream actions such as publishing content, sending notifications, or updating a database as soon as an AI generation job completes, rather than waiting on a synchronous response.
</Tip>