Waspito Third-Party OAuth API

Build connected healthcare experiences.

RESTful JSON API Expiring access tokens Signed call links

curl --request POST \
  'https://developers.waspito.com/api/v1/icers-bridge/ehealth-access/oauth/token' \
  --header 'Content-Type: application/json' \
  --data '{
    "client_id": "YOUR_CLIENT_ID",
    "client_secret": "YOUR_CLIENT_SECRET"
  }'

const response = await fetch(
  'https://developers.waspito.com/api/v1/icers-bridge/ehealth-access/oauth/token',
  {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json'
    },
    body: JSON.stringify({
      client_id: 'YOUR_CLIENT_ID',
      client_secret: 'YOUR_CLIENT_SECRET'
    })
  }
);

$response = Http::post('https://developers.waspito.com/api/v1/icers-bridge/ehealth-access/oauth/token', [
  'client_id' => 'YOUR_CLIENT_ID',
  'client_secret' => 'YOUR_CLIENT_SECRET',
]);

$accessToken = $response->json('data.access_token');

POST /oauth/token 200 · application/json

Built for connected care

Healthcare building blocks that work together.

Move from authentication to a secure consultation experience with a focused set of APIs designed around real healthcare workflows.

Application credentials

OAuth access tokens

Exchange approved credentials for a short-lived developer access token.

Controlled documentation

Protected endpoint details are revealed only to signed-in developer users.

A short path to your first call

Go from credentials to consultation in three steps.

The Waspito integration flow follows a clear server-to-server sequence. Keep credentials on your backend and expose only the generated consultation link to the patient.

Read the complete quickstart

01
Developer console

Create an application

Register your integration and securely save the client ID and one-time client secret.
02
Authentication

Generate an access token

Exchange the application credentials at the token endpoint and use the returned Bearer token for API calls.
POST /api/v1/icers-bridge/ehealth-access/oauth/token
03
Developer access

Sign in to continue

Protected endpoint pages are added to the documentation menu after Developer Console authentication.
Developer sign in →