# Developer overview

Understand what is available today before building an integration with Nugget.

## Current integration surface

Nugget has an API used by its own application, supported service connections and specific webhook receivers. An application endpoint is not automatically a supported public developer API.

> **Public API contract not published**
> Nugget does not provide self-service API keys, a public SDK or a general-purpose API access contract. Do not build an integration around copied browser credentials.

## Choose an integration path

| Your goal | Starting point |
| --- | --- |
| Connect a supported service | Use Settings, then Integrations. |
| Automate work in Nugget | Review the available workflow triggers and actions. |
| Build an external application | Define the intended operations and access model before choosing endpoints. |
| Monitor basic availability | Use the read-only health reference. |

## Read the technical guidance

[Authentication and access](https://usenugget.app/docs/developers/authentication)

[Requests and errors](https://usenugget.app/docs/developers/requests)

[Service health](https://usenugget.app/docs/developers/health)

[Webhooks and automation](https://usenugget.app/docs/developers/webhooks)

## What a public API needs

A public release needs a stable, reviewed specification, an approved authentication method, scoped permissions, documented quotas and a versioning policy. These are publication requirements, not promises of currently available features.