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.
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 accessHow the application’s session boundary differs from credentials for an external integration.Requests and errorsInterpret application API responses without treating internal endpoints as a public contract.Service healthA read-only availability check that does not require account credentials.Webhooks and automationUnderstand event boundaries before connecting an external sender.
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.