Introduction

The Condens Public API allows programmatic access to your organization’s data in Condens. It follows a simple and consistent design that makes it easy to integrate Condens with internal tools, automation scripts and third-party systems.

API base URL

The API base URL depends on the region in which your Condens data is hosted.

For accounts hosted in the EU:

https://api.condens.io

For account hosted in the US:

https://api-us.condens.io

If you’re unsure which server your account uses, check the API & MCP-Server settings page in Condens to view the assigned base URL.

Authorization

All API endpoints require authorization using an API key generated in the Condens app. API keys represent your organization and must be included in every request using the Authorization header. View the next guide for more information on Authorization.

Authorization: Bearer API_KEY

Workspace Selection

Most API endpoints accept an optional workspaceId, either as a request body parameter or as a query parameter. If your account does not have multiple workspaces enabled, this can be safely omitted. For accounts that do have multiple workspaces, the workspaceId must be provided, otherwise the server assigns the first available workspace by default.

API Design

The API uses standard REST conventions with predictable resource paths and HTTP methods. Each resource type such as Workspaces, Projects, Sessions, Users and Participants supports a list endpoint for fetching collections and a detail endpoint for fetching individual items by ID.

List endpoints are paginated and return results in pages with additional properties such as page, pageSize, total and hasNext. You can use query parameters to filter or sort these results directly on the API server to reduce the amount of data fetched.

Filtering and sorting are powered by Information Fields. They can be created or updated when creating or modifying a Project, Session or Participant. They can also be used in query parameters to narrow down or sort results.

All endpoints return JSON responses and follow consistent naming and structure. For detailed schemas, parameters and examples, refer to the API Reference. It includes the complete specification for all endpoints and properties mentioned in these guides.

Refer to the subsequent guides to learn more about Authorization, Information Fields, filtering and sorting, and pagination in detail.