> ## 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.

# Prepare your first request

> Confirm integration access, choose your environment, and prepare a request to Nimbo.

Before you start, identify what your integration needs to read or change and who on your team will maintain it. Have a Nimbo contact confirm the account, permissions, and environment for that workflow.

For product options and access questions, see [API e integraciones](https://help.nimbo-x.com/administracion/integraciones/api-e-integraciones). For technical setup, prepare your [test environment](/guides/environments) and keep credentials on your server.

<Steps>
  <Step title="Confirm your integration access">
    Describe what your software needs to read or update. Ask Nimbo to confirm the supported operations, permissions, and authentication method for that integration.
  </Step>

  <Step title="Get the correct API host">
    Use the base URL supplied for your integration and environment. `dev.nimbo-x.com` is the documentation site, not an API host. The `api.example.test` host in this site's reference is a placeholder and cannot receive API requests.

    Check whether your supplied base URL already includes `/api/v1` before adding an endpoint path. Include that prefix only once.
  </Step>

  <Step title="Set your environment">
    The examples below use `NIMBO_API_BASE_URL` for the API URL **including** `/api/v1`, with no trailing slash. Set it to the URL supplied by Nimbo. Use only synthetic records in your agreed test environment.

    ```bash theme={null}
    export NIMBO_API_BASE_URL="https://api.example.test/api/v1"
    ```

    This placeholder cannot receive requests. Webhook management uses a separate base URL; see [Webhooks](/guides/webhooks).
  </Step>

  <Step title="Obtain an access token">
    Follow [Authentication](/authentication) using the method approved for your account. Store the returned `access_token` securely as `NIMBO_ACCESS_TOKEN` in your local development environment. Do not put credentials or tokens in a committed script.
  </Step>

  <Step title="Make a read request">
    If organization access is enabled for your integration, request the current organization:

    ```bash theme={null}
    curl --include --request GET "$NIMBO_API_BASE_URL/organizations/current" \
      --header "Authorization: Bearer $NIMBO_ACCESS_TOKEN" \
      --header "Accept: application/json"
    ```
  </Step>

  <Step title="Inspect the response">
    The reference documents HTTP `200` for this operation but does not yet specify its response fields. Inspect the returned organization and confirm the fields your integration needs before creating records. A token error or unexpected organization is a reason to check access with Nimbo before proceeding.
  </Step>
</Steps>

Read [Authentication](/authentication) before adding credentials, and [Browse endpoints](/reference/overview) to find the endpoints for your integration.

Next, [create a patient](/guides/patients), [schedule an appointment](/guides/appointments), or [build a patient portal](/guides/patient-portal). See [Request conventions](/guides/request-conventions) for URL construction, dates, and error handling.