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

# Organization settings

> Read your organization's configuration - default tap redirect and network setup - and set the org-wide redirect fallback.

`GET /v1/settings` returns your organization's configuration. One field is writable; the rest are set up by Endstate during onboarding.

<CodeGroup>
  ```ts SDK theme={null}
  await endstate.settings.get();
  ```

  ```bash cURL theme={null}
  curl https://api2.endstate.io/v1/settings \
    -H "Authorization: Bearer end_sk_..."
  ```
</CodeGroup>

<Accordion title="Response">
  ```json theme={null}
  {
    "default_redirect_url": "https://brand.example",
    "default_chain_id": 84532,
    "allowed_chain_ids": [84532]
  }
  ```
</Accordion>

<ResponseField name="default_redirect_url" type="string | null">
  Where taps land when no unit or collection redirect applies. Writable.
</ResponseField>

<ResponseField name="default_chain_id" type="integer | null">
  Your organization's default network - the one collections are created on when
  `chain_id` is omitted. `null` if none is configured. Read-only.
</ResponseField>

<ResponseField name="allowed_chain_ids" type="integer[]">
  The networks enabled for your organization. An explicit `chain_id` on
  collection create must be one of these. Read-only.
</ResponseField>

## Set the default redirect

Set your organization's fallback redirect, used when a tap has no more specific destination. Send `null` to clear it.

<CodeGroup>
  ```ts SDK theme={null}
  await endstate.settings.update({
    default_redirect_url: "https://brand.example/verify",
  });
  ```

  ```bash cURL theme={null}
  curl -X PATCH https://api2.endstate.io/v1/settings \
    -H "Authorization: Bearer end_sk_..." \
    -H "Content-Type: application/json" \
    -d '{ "default_redirect_url": "https://brand.example/verify" }'
  ```
</CodeGroup>

This is the lowest-priority redirect: a redirect set on the unit or its collection wins. See [Tap redirects](/concepts/tap-redirects) for the full resolution order.

## Network configuration

`default_chain_id` and `allowed_chain_ids` are read-only and configured by Endstate. Most integrations never send a `chain_id` at all - omit it and collections are created on your default network. If you do send one explicitly, it must appear in `allowed_chain_ids`, or the request fails with `validation.failed`.

To change either, contact Endstate.

## Other settings

* [Publishable keys](/settings/publishable-keys) - the client-safe key identifying your organization.
* [CORS origins](/settings/cors-origins) - which web origins may call the API from a browser. Managed at `/v1/settings/cors-origins`.

***

## Next steps

<CardGroup cols={2}>
  <Card title="Tap redirects" icon="corner-up-right" href="/concepts/tap-redirects">
    Set redirects per unit, per collection, or org-wide, and how they resolve.
  </Card>

  <Card title="Collections" icon="layers" href="/concepts/collections">
    How networks apply when you create a collection.
  </Card>
</CardGroup>