C
Coherta Developer Portal Overview and quickstart
Start here

Everything you need before opening the full API reference.

Use this page as the front door to the Coherta API. It gives you the fast path to authentication, highlights the main endpoint groups, and lets you validate your credentials directly against the token endpoint before you move into the detailed reference.

122 Public endpoints
83 Protected routes
39 Open routes
34 Reference groups

Authentication first

Most integrations start by obtaining a bearer token. The quickstart below includes both code samples and a live token request form.

JWT bearer token Live validation Header builder

Separate API reference

The detailed endpoint documentation now lives on its own page, making the landing page cleaner and easier to use as a first stop.

Dedicated reference page Endpoint search Three-column layout

Bearer Token Quickstart

You do not need to assemble the JWT yourself. Request a token with your credentials, verify that the API returns an access_token, and then send it as Authorization: Bearer <access_token> on protected requests.

1
Request a token

Call POST /token with username and password. The endpoint accepts JSON and form data.

2
Confirm the response

Look for an access_token in the response body. This page can validate that for you live against the endpoint.

3
Reuse it as a bearer token

Send Authorization: Bearer <access_token> to protected endpoints, or renew an expired token with POST /token/renew.

cURL: request a token
curl -X POST "https://api.coherta.com/token" \
  -H "Content-Type: application/json" \
  -d "{\"username\":\"demo\",\"password\":\"secret\"}"
JavaScript: use the token
const token = "PASTE_ACCESS_TOKEN";

const response = await fetch("https://api.coherta.com/users/me", {
  headers: {
    Authorization: `Bearer ${token}`
  }
});

Request a token on this page

Use your real credentials to validate that the token endpoint returns an access token. The returned token can then be reused in the header builder below.

Ready to send a request to /token.
Token response
{}

When a token request succeeds, the returned access token is filled in automatically.

Ready-to-send header
Authorization: Bearer PASTE_ACCESS_TOKEN