How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

OpenObserve Organizations API

Organizations retrieval & management operations

OpenObserve Organizations API is one of 33 APIs that OpenObserve publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Organization. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a GitHub repository.

This API exposes 18 operations across 11 paths, and defines 13 schemas. It is described by OpenAPI 3.1.0, at version 0.90.0.

Requests are made against the base URL https://api.openobserve.ai.

18 operations 11 paths 13 schemas 2 DELETE7 GET6 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
0.90.0
Base URL
https://api.openobserve.ai
Authentication
API Key, HTTP Basic
License
AGPL-3.0
Resource Areas
1

Authentication & Security 2

OpenObserve Organizations API declares 2 security schemes for authenticating requests. An API key is passed in the header as Authorization (Authorization). It accepts HTTP basic authentication (BasicAuth).

Paths & Operations 18

Across 11 paths, the API surfaces 18 operations — 2 DELETE, 7 GET, 6 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

Organizations 18

Organizations retrieval & management operations

GET
/api/organizations
Get user's organizations
GetUserOrganizations → 200
POST
/api/organizations
Create new organization
CreateOrganization body → 200
POST
/api/{org_id}/organizations/assume_service_account
Assume a service account in a target organization
AssumeServiceAccount 1 param body → 200400403500501
GET
/api/{org_id}/passcode
Get user's ingestion token
GetOrganizationUserIngestToken 1 param → 200404
PUT
/api/{org_id}/passcode
Update user's ingestion token
UpdateOrganizationUserIngestToken 1 param → 200404
PUT
/api/{org_id}/rename
Rename organization
RenameOrganization 1 param body → 200
GET
/api/{org_id}/rumtoken
Get user's RUM ingestion token
GetOrganizationUserRumIngestToken 1 param → 200404
PUT
/api/{org_id}/rumtoken
Update user's RUM ingestion token
UpdateOrganizationUserRumIngestToken 1 param → 200404
POST
/api/{org_id}/rumtoken
Create user's RUM ingestion token
CreateOrganizationUserRumIngestToken 1 param → 200404
GET
/api/{org_id}/settings
Get organization settings
OrganizationSettingGet 1 param → 200400
POST
/api/{org_id}/settings
Update organization settings
OrganizationSettingCreate 1 param body → 200400
GET
/api/{org_id}/settings/v2
List all resolved system settings
SystemSettingListResolved 3 params → 200400
POST
/api/{org_id}/settings/v2
Set organization-level setting
SystemSettingSetOrg 1 param body → 200400
POST
/api/{org_id}/settings/v2/user/{user_id}
Set user-level setting
SystemSettingSetUser 2 params body → 200400
DELETE
/api/{org_id}/settings/v2/user/{user_id}/{key}
Delete user-level setting
SystemSettingDeleteUser 3 params → 200400404
GET
/api/{org_id}/settings/v2/{key}
Get resolved system setting
SystemSettingGetResolved 3 params → 200400
DELETE
/api/{org_id}/settings/v2/{key}
Delete organization-level setting
SystemSettingDeleteOrg 2 params → 200400404
GET
/api/{org_id}/summary
Get organization summary
GetOrganizationSummary 1 param → 200

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are SystemSetting (12 properties), OrgDetails (9 properties), AssumeServiceAccountResponse (5 properties), SystemSettingPayload (4 properties). Each schema is shown below with its type and property counts.

ServiceAccountTokenInfo
object
3 properties 3 required
RumIngestionToken
object
2 properties 1 required
AssumeServiceAccountResponse
object
Response from assume service account operation Contains the session credentials needed to access the target organization.
5 properties 5 required
CrossLinkField
object
2 properties 1 required
SettingScope
string
Setting scope levels
IngestionPasscode
object
2 properties 2 required
AssumeServiceAccountRequest
object
Request to assume a service account in a target organization This allows meta service accounts to obtain temporary session tokens for accessing a target organi…
3 properties 1 required
OrgDetails
object
9 properties 8 required
SystemSetting
object
A system setting record
12 properties 3 required
OrgUser
object
3 properties 3 required
CrossLink
object
A cross-link entry for drill-down/navigation from log/trace records
3 properties 2 required
Organization
object
4 properties 1 required
SystemSettingPayload
object
Request to create or update a setting
4 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

openobserve-organizations-api-openapi.yml Raw ↑

Other APIs OpenObserve publishes across the network.

OpenObserve Actions API
OpenObserve Alerts API
OpenObserve Clusters API
OpenObserve Dashboards API
OpenObserve Folders API
OpenObserve Functions API
OpenObserve Groups API
OpenObserve Incidents API
OpenObserve Key API
OpenObserve Keys API
OpenObserve KV API
OpenObserve Logs API
Where this information came from

This is an independent, third-party profile of OpenObserve Organizations API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.