> For the complete documentation index, see [llms.txt](https://docs.fastn.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fastn.ai/embed/api-keys/finding-your-org-identifier.md).

# Find your org identifier

The customer identifier names the customer a widget embed is for, in the `x-org-id` header of the token request. Only the token request needs it: the iframe URL takes the token alone, because the token already carries the customer. Getting the right identifier is necessary for anything to work.

### Two identifiers work

`x-org-id` accepts either:

* **fastn's id for the customer**, or
* **your external reference**: the id you gave the customer when you registered it (`orgId` on `POST /api/v1/orgs`). Using your own id means you never have to store fastn's. If you created a customer without one, fastn stored its slug as the external reference at creation time.

### Where fastn's id comes from

Each customer in your fastn workspace has an internal id. You create customers under **Operate → Customers** (see [Managing Customers](https://docs.fastn.ai/operate/customers/managing-customers.md)).

To find it, open **Operate → Customers** in the dashboard and click the customer. The address bar changes to `app.fastn.dev/customers/<id>`: the last part of that URL is the customer's id. Copy it from there.

{% hint style="info" %}
Create a separate test customer for development and use its id locally, so test connections never land on a real customer.
{% endhint %}

### Using it

Once you have the identifier, send it as the `x-org-id` header on the token request, or as `orgId` in the body. Nothing else needs it: the iframe URL is just `?token=<token>`. A key limited to a single customer is the one exception: it takes only fastn's id, in `orgId`. See [Generating Embed Tokens](https://docs.fastn.ai/embed/embedding/generating-embed-tokens.md).

In production, look the identifier up per request from the signed-in person's company rather than fixing one value, so each customer gets their own token. For local testing against a single test customer, an environment variable is fine:

```
FASTN_ORG_ID=<test-customer-id>
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fastn.ai/embed/api-keys/finding-your-org-identifier.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
