> 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/tutorials/developer/finding-your-org-identifier.md). # Finding your org identifier The `endOrgId` identifies the customer a widget embed is for. Both the token endpoint and the iframe URL require it. Getting the right identifier is necessary for anything to work. ### It must be the customer UUID `endOrgId` must be the customer's internal UUID. The customer **slug** (e.g., `katana-customer`) does not work in its place. ### Where the UUID comes from Each customer in your Fastn workspace has an internal UUID. You create customers under **Settings → Customers** (see [Managing Customers](/tutorials/saas-admin/managing-customers.md)). The customer record in the dashboard shows: Name, Slug, Status, Customer Admin, and Created date. It does **not** display the UUID — there is no UUID or External ID field in the Customers UI. To retrieve the UUID today, open the customer in the dashboard and read it from the page state using your browser's developer tools. > **VERIFY:** This is a confirmed gap — the customer UUID is not exposed anywhere in the Customers UI (validated on the live platform). The Embed tab refers to this value as `YOUR_CUSTOMER_ID` / `customer_id`. Confirm the recommended retrieval method, and update this page if the UUID becomes available directly in the UI or via an API endpoint. ### Using it Once you have the UUID, pass it as `endOrgId` in: * The token request body (`{ endOrgId, userEmail, userName }`) * The iframe URL for user-level embeds (`?tenant-id=&token=`) Store it in an environment variable rather than hardcoding it, so it can change per environment (test customer vs production customer). ``` FASTN_END_ORG_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/tutorials/developer/finding-your-org-identifier.md?ask=&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.