Files
zitadel/docs
Livio Spring 6b407ab8f2 feat(api): move organization api (#11045)
# Which Problems Are Solved

As part of our efforts to simplify the structure and versions of our
APIs, were moving all existing v2beta endpoints to v2 and deprecate
them. They will be removed in Zitadel V5.

# How the Problems Are Solved

- This PR moves the remaining organization v2beta service endpoints to a
corresponding v2 version. The v2beta service and all endpoints are
deprecated.
- The v2beta endpoints are removed from the docs.
- The comments and have been improved and, where not already done, moved
from swagger annotations to proto.
- When listing Organizations can now be sorted by creation date as well.
- The custom `org_id` parameter in the `AddOrganizationRequest` message
has been deprecated in favor of `organization_id`

# Additional Changes

None

# Additional Context

- relates to #10772 
- Directly targeting v4.x since main needs to be cleaned up first with
the relation table and permission checks.
2025-11-13 08:43:38 +01:00
..
2025-10-09 16:53:19 +02:00
2025-10-09 16:53:19 +02:00
2025-10-09 16:53:19 +02:00
2025-10-09 16:53:19 +02:00

ZITADEL-Docs

This website is built using Docusaurus 2, a modern static website generator.

The documentation is part of the ZITADEL monorepo and uses pnpm and Nx for development and build processes.

Quick Start

Run the following commands from the repositorys root directory to install all dependencies needed. Using Corepack makes sure you have the pnpm version intalled that is declared in .

corepack enable
pnpm install

Start a docs server

# Start development server with live-reloading
pnpm nx run @zitadel/docs:dev

# Or serve a production build
pnpm nx run @zitadel/docs:start

The site will be available at http://localhost:3100

Add new Sites to existing Topics

To add a new site to the already existing structure simply save the md file into the corresponding folder and append the sites id int the file sidebars.js.

If you are introducing new APIs (gRPC), you need to add a new entry to docusaurus.config.js under the plugins section.

Build Process

The documentation build process automatically:

  1. Downloads required protoc plugins - Ensures protoc-gen-connect-openapi is available
  2. Generates gRPC documentation - Creates API docs from proto files
  3. Generates API documentation - Creates OpenAPI specification docs
  4. Copies configuration files - Includes configuration examples
  5. Builds the Docusaurus site - Generates the final static site