Skip to content

Base URLs & methods

Kendis exposes its APIs through two methods. They share the same authentication and JSON style; they differ in how your company (tenant) is identified in the URL and in the path version segment. This page is the single place to confirm which host an endpoint uses.

Method A — Versioned subdomain method (/api/v1)

Your company is identified by the subdomain. The API version lives in the path.

https://{yourcompany}.kendis.io/api/v1/...
  • Tenant = your subdomain. If your Kendis URL is https://acme.kendis.io, then your base is https://acme.kendis.io/api/v1/....
  • No company prefix in the path. The tenant comes from the host and your API key.
  • Used today by the Risk and Strategic Themes & OKRs APIs.

Method B — Legacy path-prefix method (/api/<companyPrefix>)

Your company is identified by a path segment on a shared host.

https://rest.kendis.io/api/<companyPrefix>/...
  • Tenant = <companyPrefix>. Find it in your Kendis login URL — https://<companyPrefix>.kendis.io.
  • There is no endpoint that returns your prefix — if you don't know it, ask your Kendis administrator.
  • Used today by the PI Board Items and PI Objectives APIs.

Which method does each API use?

API Method today Base URL
PI Board Items B — legacy path prefix https://rest.kendis.io/api/<companyPrefix>/…
PI Objectives B — legacy path prefix https://rest.kendis.io/api/<companyPrefix>/…
Risk A — versioned subdomain https://{yourcompany}.kendis.io/api/v1/…
Strategic Themes & OKRs A — versioned subdomain https://{yourcompany}.kendis.io/api/v1/…

Each API's Endpoints page always shows the exact, correct base URL for that API — when in doubt, follow the example there.

Domain restrictions

For requests originating from the kendis.io domain:

  • The API can only be reached via the rest.kendis.io subdomain (Method B). A request from any other *.kendis.io host that isn't rest.kendis.io is denied.

For requests from other domains (your servers, scripts, BI tools): no domain-specific restriction applies — the standard Basic auth check is all that matters.

A note on consolidation

The versioned /api/v1 method is the forward-looking method, and the PI Board Items and PI Objectives endpoints already exist there in addition to the legacy host. We document each API on the host its current guide is published against, so your existing integrations keep working unchanged.

Planning a new integration?

If you're building something new and want to standardise on a single host, ask your Kendis representative to confirm the recommended base URL for PI Board data before pointing production traffic at /api/v1 for those endpoints.