Environments

Audience: Admins, Developers, Solution Architects

Purpose: Explains how Kizen production environments work so you can correctly select API base URLs, configure authentication, and avoid cross-environment integration errors.

Overview

The Kizen environment refers to the specific production instance of the Kizen 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

Kizen currently supports the following production environments:

Environment	API Base URL	Web App URL	Typical Use Case
GO	https://app.go.kizen.com/api	https://go.kizen.com	Primary production environment
FMO	https://app.fmo.kizen.com/api	https://fmo.kizen.com	Alternate production environment, specific to FMOs

---

Environment Isolation and Authentication

Each Kizen 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 documentation.

---

Testing, Deployment, and Troubleshooting

Kizen 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 Records, 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:

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:

GET /objects

Full request:

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

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

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 Kizen 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 before making your first API call.

Related Topics

• Authentication

• Objects

• Records API