> For the complete documentation index, see [llms.txt](https://developer.kizen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.kizen.com/docs/developers/environments.md). # Environments {% hint style="success" %} **Audience:** Admins, Developers, Solution Architects **Purpose:** Explains how space.vars.Kizen\_company\_name production environments work so you can correctly select API base URLs, configure authentication, and avoid cross-environment integration errors. {% endhint %} ## Overview The space.vars.Kizen\_company\_name environment refers to the specific production instance of the space.vars.Kizen\_company\_name platform where a business account is hosted. Each environment has its own Web App URL and API base URL and operates as a separate production cluster. When building integrations, selecting the correct environment is critical. API requests sent to the wrong environment will fail authentication or return unexpected results because credentials, data, and configurations are not shared across environments. ### Available Environments space.vars.Kizen\_company\_name currently supports the following production environments:
EnvironmentAPI Base URLWeb App URLTypical Use Case
GOhttps://app.go.kizen.com/apihttps://go.kizen.comPrimary production environment
FMOhttps://app.fmo.kizen.com/apihttps://fmo.kizen.comAlternate production environment, specific to FMOs
*** ## Environment Isolation and Authentication Each space.vars.Kizen\_company\_name environment is fully isolated. Databases, business accounts, users, API tokens, and OAuth contexts are not shared across environments. Data created in one environment is not accessible from another. Authentication is environment-specific. Credentials are issued within a specific environment and are valid only for that environment’s API base URL. A token generated in `go` cannot authenticate against `fmo`. If you receive a `401 Unauthorized` response and your credentials are correct, verify that: * The API base URL matches your UI environment * The token was generated in the same environment you are calling For additional guidance, see the [Authentication](/docs/developers/authentication.md) documentation. *** ## Testing, Deployment, and Troubleshooting space.vars.Kizen\_company\_name does not provide public sandbox environments, so integrations operate directly against production environments. Use a non-critical production account for development testing and avoid destructive operations on live business data. Before deploying updates, confirm that environment variables reference the correct API base URL and that environment-specific credentials are properly configured. Misconfigured environment values are a common cause of integration failures. Common symptoms of an environment mismatch include `401 Unauthorized` errors despite valid credentials, `404 Not Found` responses for known space.vars.entities, missing data, or OAuth flows that succeed while API calls fail. In most cases, the API request is being sent to the wrong environment. Verify the Web App URL, the API base URL, and the environment where the token was generated before investigating further.
API Base URL Structure #### About the API Base URL Structure The general API format is: ```bash https://app.{environment}.kizen.com/api ``` Replace `{environment}` with either: * `go` * `fmo` All endpoints documented in the API Reference are relative to this base URL. Example endpoint: ```bash GET /objects ``` Full request: ```bash https://app.go.kizen.com/api/objects ``` #### Using the Correct Environment in API Calls Environment selection only affects the base URL. All endpoints remain the same. **Example: GO Environment** ```bash curl \ -H "x-api-key: {api_key}" \ -H "x-user-id: {user_id}" \ -H "x-business-id: {business_id}" \ https://app.go.kizen.com/api/objects ``` **Example: FMO Environment** ```bash curl \ -H "x-api-key: {api_key}" \ -H "x-user-id: {user_id}" \ -H "x-business-id: {business_id}" \ https://app.fmo.kizen.com/api/objects ``` If the base URL does not match the environment where the token was issued, the request will fail.
*** ## What’s Next Next, confirm which space.vars.Kizen\_company\_name environment your business is hosted in by checking the Web App URL and verifying the matching API base URL. From there, generate credentials within that environment and proceed to [Authentication](/docs/developers/authentication.md) before making your first API call.
Related Topics * [Authentication](/docs/developers/authentication.md) * [Objects](/docs/concepts/objects.md) * [Records API](/docs/concepts/objects/records/records-apis.md)
--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://developer.kizen.com/docs/developers/environments.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.