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

# Build with Nimbo

> Find API contracts and integration guidance for connecting your software to Nimbo.

Use Nimbo Developers to connect your software to Nimbo through HTTP APIs and webhooks. Start by confirming the API access and environment available to your organization with the Nimbo team.

<Columns cols={2}>
  <Card title="Prepare your integration" icon="plug" href="/quickstart">
    Confirm your use case, credentials, and API host before your first request.
  </Card>

  <Card title="Browse API endpoints" icon="code" href="/api-reference/patient-management/post-people">
    Find endpoints for catalogs, clinical workflows, scheduling, billing, and webhooks.
  </Card>
</Columns>

## Build an integration

Follow a complete workflow after setting up access: [create a patient](/guides/patients), [schedule an appointment](/guides/appointments), [build a patient portal](/guides/patient-portal), [connect charges and invoicing](/guides/billing), or [receive webhook events](/guides/webhooks).

For a CRM, form, or scheduling bot, start with the patient and appointment guides. Keep credentials on your server and decide which system sends reminders before enabling messages. Prepare your [test environment](/guides/environments) and use [Troubleshooting](/guides/troubleshooting) to diagnose failures.

## API documentation and product help

This site is for developers integrating with Nimbo. For instructions on using Nimbo's application, visit the [Nimbo help center](https://help.nimbo-x.com). Its [API and integrations overview](https://help.nimbo-x.com/administracion/integraciones/api-e-integraciones) explains integration options and how to prepare a request with your team.

## Get integration support

[Contact Nimbo](https://www.nimbo-x.com/contacto) with your integration's purpose, the environment you need, and the operations you expect to use. Share request IDs and error status codes when troubleshooting; keep credentials and patient information out of support examples.