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

# Embed Portal

> Manage API keys, webhooks, team members, and monitor your integration

**URL:** `https://embed.nova.dweet.com`

## Environments

Sandbox and production are completely separate (API keys, webhooks, data). Toggle with the environment switcher:

* `https://embed.nova.dweet.com/sandbox`
* `https://embed.nova.dweet.com/production`

## Roles

| Role   | Permissions                                          |
| ------ | ---------------------------------------------------- |
| Admin  | Manage API keys, webhook endpoints, and team members |
| Member | View-only access                                     |

## API key management

Go to **API Keys** to create, view, and revoke keys.

<Warning>
  The full key is shown once at creation. Store it securely.
</Warning>

Revoked keys immediately return `401 Unauthorized`. You can restore revoked keys from the **Revoked Keys** section.

## Webhook endpoints

Configure up to **5 endpoints per environment** under **Webhooks**. Each has its own signing secret and can be enabled/disabled independently.

Use the **Webhook Playground** to send test webhooks and verify signature verification.

## Delivery history

View webhook delivery attempts under **Webhooks > Delivery History**.

| Column   | Description                                       |
| -------- | ------------------------------------------------- |
| Status   | Pending, Processing, Delivered, or Failed         |
| Event    | Score Completed, Score Failed, or Batch Completed |
| Endpoint | Target webhook URL                                |
| Tenant   | Tenant ID from the original request               |
| Attempts | Number of delivery attempts                       |

**Filters:** Status, event type, endpoint, time range (24h, 7d, 30d).

Click any row for full details: metadata, request payload, and per-attempt history.

### Retrying failed deliveries

Admins can manually retry failed deliveries (all automatic retries exhausted) from the delivery detail view. The endpoint must still exist and be enabled.

## Retrying failed scoring runs

Admins can retry permanently failed scoring runs from the **Monitoring** page or the **Dashboard** Recent Activity table. Open the run detail drawer for a failed run and click **Retry Run** in the header.

Retry is available when all of these are true:

* The error is transient (`TASK_STUCK`, `TIMEOUT`, `AI_SCORING_FAILED`, or `MAX_RETRIES_EXCEEDED`)
* The run is not part of a batch
* The manual retry limit (2) hasn't been reached
* The original resume and job description are still available

Non-admin members see a message explaining that only admins can retry. Runs with non-retryable errors (like `RESUME_FETCH_FAILED`) show a reason why retry isn't available.

## Team management

View and manage your team from **Team**. Admins can invite members, change roles, and remove members.

Invites are sent via email with an OTP sign-in link.

## Dashboard and Usage

The **Dashboard** shows overview stats: total requests, success rate, average latency, and scores generated. **Usage** breaks down metrics by tenant. Time ranges: 24h, 7d, 30d, 90d.

## Support

Email **[nova@dweet.com](mailto:nova@dweet.com)**.