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

# For developers

> Start here if you are integrating Nectar into your product or data platform.

<Tip>
  Need help in this area? See [Get Started FAQ](/docs/platform/getting-started-faq).
</Tip>

This page helps developers quickly find the right technical docs.

If you are trying to use the Nectar dashboard day to day, use the [Knowledge Base](/docs/platform/getting-started). If you are building an integration, follow the path below.

## Developer quick start path

<Steps>
  <Step title="Create an API key in Settings">
    In Nectar, go to [**Settings → Organization → Developer**](https://dash.nectarclimate.com/settings/organization/developer), then click **Add API key**. Enter a name, choose **Production** or **Development**, set an expiration, click **Create**, then copy the key from the table and store it in your secret manager.

    If **Developer** is missing from Organization settings, you are not an org admin on a native docs-enabled organization — ask an Admin Team member.

    **Development** here is the API-key environment. It is not the same as [Sandbox testing](/docs/developer-guide/sandbox-testing), which uses Nectar's mock utility account.
  </Step>

  <Step title="Run the API getting-started flow">
    Follow [Getting started with the API](/docs/developer-guide/getting-started) to authenticate and make your
    first request.
  </Step>

  <Step title="Set up your test environment">
    Use [Sandbox testing](/docs/developer-guide/sandbox-testing) (Nectar's mock utility account) to validate
    your integration safely before going live — separate from the **Development** API-key environment.
  </Step>

  <Step title="Implement integration features">
    Add [Webhooks](/docs/developer-guide/webhooks) for event-driven workflows and
    [Connection invitations](/docs/developer-guide/connection-invitations) if you embed Nectar's connection UI
    in your product.
  </Step>

  <Step title="Use API Reference for endpoint details">
    Once your flow is working, use the [API Reference](/docs/api-reference) for full schema and endpoint
    behavior. For new integrations, use **v2.2**.
  </Step>
</Steps>

## What belongs where?

| You need to...                          | Best place to go                                                                                              |
| --------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| Understand platform workflows and UI    | [Knowledge Base](/docs/platform/getting-started)                                                                   |
| Get integration-ready quickly           | [Developer guide](/docs/developer-guide/for-developers)                                                            |
| Inspect request/response schemas        | [API Reference](/docs/api-reference)                                                                               |
| Learn data semantics behind API objects | [Data model overview](/docs/developer-guide/data-model/overview) and [Methodology](/docs/platform/methodology/overview) |

## Common developer links

<CardGroup cols={2}>
  <Card title="Developer guide home" icon="book-open" href="/docs/developer-guide/for-developers">
    Main developer onboarding page with the recommended implementation order.
  </Card>

  <Card title="API getting started" icon="rocket" href="/docs/developer-guide/getting-started">
    Authenticate, test your key, and make your first API request.
  </Card>

  <Card title="Sandbox testing" icon="flask" href="/docs/developer-guide/sandbox-testing">
    Validate flows with Nectar's mock utility account before production rollout.
  </Card>

  <Card title="API Reference" icon="square-terminal" href="/docs/api-reference">
    Endpoint-by-endpoint documentation for v2.0, v2.1, and v2.2.
  </Card>
</CardGroup>