Orita Resolution API v2

Resolve the right provider and time.Then confirm it safely.

Search your provider network, apply eligibility rules, rank valid provider-time options, explain every result, and complete the booking lifecycle through one API.

Run your first resolution Watch 45-sec demo

REST APINode SDKPython SDKMCP serverA2A agentSigned webhooks

provider-resolution.ts

import { OritaClient } from "orita-sdk";

const orita = new OritaClient({
  apiKey: process.env.ORITA_API_KEY
});

const resolution = await orita.resolveScheduling({
  serviceId: "svc_therapy",
  dateRange: {
    from: "2026-08-05",
    to: "2026-08-12",
    timezone: "America/New_York"
  },
  constraints: {
    languageCodes: { anyOf: ["es"] },
    modalityCodes: { anyOf: ["virtual"] },
    acceptsNewClients: true
  },
  preferences: {
    dayParts: ["afternoon"],
    earliestAvailable: true
  },
  limit: 5
});

await orita.holdOption(
  resolution.resolutionId,
  resolution.options[0].optionId
);

const booking = await orita.confirmResolution(
  resolution.resolutionId,
  {
    optionId: resolution.options[0].optionId,
    customer: {
      name: "James Park",
      email: "james@example.com"
    }
  }
);

Eligibility checkedAvailability verifiedConflict protectedWebhook emitted

Provider graph

A structured model for the professionals and services inside your application.

Professionals and organizations
Services and attributes
Profile readiness

Resolution engine

Turn a customer need into valid provider-time options.

Hard constraints
Soft preferences
Explainable ranking

Safe execution

Move from selected option to confirmed booking without race conditions.

Temporary holds
Atomic confirmation
Idempotency

Lifecycle synchronization

Keep your agent and internal systems aligned after every change.

Signed events
Retries and replay
Delivery logs

Quickstart

Choose the flow that matches the request.

Use provider resolution when the customer knows what they need but not who should handle it. Use direct booking when the provider is already known.

Send the customer need

Pass the service, constraints, preferences, and date range.

Receive explained options

Orita returns eligible providers, valid slots, scores, and reasons.

Confirm safely

Optionally hold the slot, then confirm with an idempotency key.

Listen for lifecycle events

Update your application from signed booking webhooks.

unknown-provider.ts

const resolution = await orita.resolveScheduling({
  serviceId: "svc_therapy",
  constraints: {
    languageCodes: { anyOf: ["es"] },
    modalityCodes: { anyOf: ["virtual"] }
  },
  preferences: {
    dayParts: ["afternoon"]
  },
  dateRange: {
    from: "2026-08-05",
    to: "2026-08-12"
  }
});

const booking = await orita.confirmResolution(
  resolution.resolutionId,
  {
    optionId: resolution.options[0].optionId,
    customer: {
      name: "James Park",
      email: "james@example.com"
    }
  }
);

Resolution response

Every option tells you why it qualified.

A developer can inspect the providers searched, the rules applied, the options returned, and the reasons other providers were excluded.

resolution-response.json

{
  "resolutionId": "res_7812",
  "status": "resolved",
  "expiresAt": "2026-08-01T14:07:00Z",
  "summary": {
    "providersScanned": 126,
    "eligibleProviders": 14,
    "providersWithAvailability": 4,
    "optionsReturned": 5
  },
  "options": [
    {
      "optionId": "opt_92ab",
      "provider": {
        "id": "pro_82fa1",
        "displayName": "Dr. Ana García"
      },
      "slot": {
        "start": "2026-08-05T15:00:00-04:00"
      },
      "score": 94,
      "matchedConstraints": [
        "service_supported",
        "language_match",
        "modality_match",
        "availability_valid"
      ],
      "reason": "Matches every required condition and is the earliest available afternoon appointment."
    }
  ],
  "exclusions": {
    "serviceNotSupported": 28,
    "notAcceptingNewClients": 12,
    "noAvailability": 22
  },
  "warnings": []
}

Top option

Dr. Ana García

Tuesday · 3:00 PM · Virtual

Service supportedSpanish matchVirtual supportedAccepting new clientsAvailability verifiedPreferred afternoon

Matches every required condition and is the earliest available afternoon appointment.

Filtering funnel

126Providers scanned

14Eligible providers

4Providers with verified availability

5Options returned

Why options were excluded

Service not supported28

Not accepting new clients12

No verified availability22

Hard constraints

The option is invalid if one fails.

Provider is active
Service is supported
Required modality
Accepting new clients
Verified availability
No calendar conflict

Preferences

They change ranking, not eligibility.

Preferred language
Preferred daypart
Earliest available
Provider continuity
Workload balance
Preferred location

Reliable execution

A recommendation is useful only if you can safely execute it.

Orita protects the transition from a ranked option to a confirmed booking and keeps every downstream system synchronized.

Resolve

Return valid, explained options.

Hold

Temporarily reserve the selected slot.

Revalidate

Check eligibility and availability again.

Confirm once

Use atomic, idempotent confirmation.

Synchronize

Deliver signed lifecycle events.

Idempotency

Safely retry resolutions and confirmations without duplicate bookings.

Conflict protection

Internal and connected-calendar conflicts are checked before confirmation.

Booking lineage

Preserve state through reschedules, replacements, and cancellations.

Webhook delivery

Retry, inspect, and replay signed events using stable event IDs.

Provider graph

Model professionals, not calendar accounts.

Store the structured service and provider attributes your application needs to evaluate eligibility before checking a calendar.

Profession and specialtiesServices and durationLanguages and modalitiesLocations and regionsAccepting-new-client statusAvailability and scheduling rulesProfile versionsCustom organization attributes

Read provider graph docs Onboarding API

provider.json

{
  "id": "pro_82fa1",
  "organizationId": "org_123",
  "displayName": "Dr. Ana García",
  "professionCode": "clinical_psychologist",
  "languageCodes": ["es", "en"],
  "specialtyIds": ["anxiety", "cbt"],
  "modalityCodes": ["virtual"],
  "acceptsNewClients": true,
  "timezone": "America/New_York",
  "profileVersion": 12,
  "searchable": true
}

SDKs, REST, and MCP

Use the interface that fits your application.

Orita works through plain HTTP, official Node and Python clients, or native MCP tools for AI environments.

Node SDK

Typed methods for resolution, holds, confirmation, and booking lifecycle.

npm install orita-sdkOpen docs

Python SDK

Python-native methods for provider networks and resolution workflows.

pip install orita-sdkOpen docs

REST API

Use every capability from any language or framework that can make HTTP requests.

https://orita.online/api/v1Open docs

MCP server

Expose provider-resolution tools directly to Claude, Cursor, and compatible agents.

https://orita.online/api/mcpOpen docs

A2A agent

Agent-to-agent service transactions. External agents discover Orita, resolve providers, and confirm bookings through A2A v1.0.

/.well-known/agent-card.jsonOpen docs

Native MCP provider resolution

Let compatible agents resolve providers, inspect explanations, hold an option, and confirm the selected booking using deterministic Orita responses.

resolve_schedulingget_resolutionhold_scheduling_optionconfirm_scheduling_resolutionrelease_scheduling_option

{
  "mcpServers": {
    "orita": {
      "url": "https://orita.online/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ORITA_API_KEY"
      }
    }
  }
}

Test without writing code

Run the full collection in Postman

6 folders · 15 requests · automatic variable saving. Adds your API key, saves resolutionId and optionId automatically between steps.

Run in Postman Download collection JSON

Webhooks and observability

Know what happened after every API call.

Receive signed lifecycle events, inspect delivery attempts, replay failed events, and track resolution and booking performance.

resolution.resolvedresolution.zero_resultsoption.heldbooking.confirmedbooking.rescheduledbooking.cancelledbooking.completedprofessional.updated

Delivery logs

Inspect event IDs, attempts, status codes, response excerpts, and latency.

Resolution analytics

Track success rates, zero-result reasons, conversion, and cancellation performance.

booking-confirmed.webhook.json

{
  "id": "evt_123",
  "type": "booking.confirmed",
  "createdAt": "2026-08-01T14:02:04Z",
  "organizationId": "org_123",
  "attempt": 1,
  "data": {
    "bookingId": "bk_18382",
    "resolutionId": "res_7812",
    "status": "confirmed"
  }
}

API reference

Endpoints grouped by the job you are completing.

Endpoints grouped by the job you are completing — from onboarding providers to completing the booking lifecycle.

Resolution

Search, rank, explain, hold, and confirm provider-time options.

POST

/api/v2/resolutions

Create an explainable provider resolution.

GET

/api/v2/resolutions/:id

Retrieve a stored resolution and its explanations.

POST

/api/v2/resolutions/:id/options/:optionId/hold

Temporarily reserve an option while the user confirms.

POST

/api/v2/resolutions/:id/confirm

Revalidate and atomically create the booking.

Provider graph

Model and manage the professionals inside your application.

POST

/api/v1/professionals

Programmatically onboard a professional.

GET

/api/v1/professionals

Search providers by structured attributes.

POST

/api/v1/event-types

Create services and scheduling rules.

POST

/api/v1/availability

Create provider availability schedules.

Booking lifecycle

Manage direct bookings and every lifecycle transition.

POST

/api/v1/bookings

Create a booking when the provider is already known.

GET

/api/v1/bookings/:id

Retrieve current booking state.

POST

/api/v1/bookings/:id/reschedule

Reschedule while preserving booking lineage.

POST

/api/v1/bookings/:id/cancel

Cancel a booking and emit lifecycle events.

Operations

Observe, synchronize, and debug production workflows.

PUT

/api/v1/webhooks

Configure signed lifecycle event delivery.

GET

/api/v1/webhooks/deliveries

Inspect attempts, response codes, and latency.

GET

/api/v1/analytics

Read resolution and booking performance metrics.

POST

/api/v1/webhooks

Send a test event to your endpoint.

Open complete API reference Errors and zero-result guide

Examples

Start from a complete provider-resolution workflow.

Complete provider-resolution workflows: onboard, resolve, hold, approve, confirm, and synchronize.

Behavioral health routing

Resolve a virtual therapist by language, specialty, and availability.

View example

AI receptionist

Turn a natural-language request into an explainable provider and booking.

View example

Next.js provider marketplace

Build provider onboarding, resolution, confirmation, and webhook sync.

View example

Start building

Resolve the right professional and book the right time.

Create an account, import test providers, and run your first explainable provider resolution.

Get your API key Read the Resolution API docs

import { OritaClient } from "orita-sdk"; const orita = new OritaClient({ apiKey: process.env.ORITA_API_KEY }); const resolution = await orita.resolveScheduling({ serviceId: "svc_therapy", dateRange: { from: "2026-08-05", to: "2026-08-12", timezone: "America/New_York" }, constraints: { languageCodes: { anyOf: ["es"] }, modalityCodes: { anyOf: ["virtual"] }, acceptsNewClients: true }, preferences: { dayParts: ["afternoon"], earliestAvailable: true }, limit: 5 }); await orita.holdOption( resolution.resolutionId, resolution.options[0].optionId ); const booking = await orita.confirmResolution( resolution.resolutionId, { optionId: resolution.options[0].optionId, customer: { name: "James Park", email: "james@example.com" } } );

const resolution = await orita.resolveScheduling({ serviceId: "svc_therapy", constraints: { languageCodes: { anyOf: ["es"] }, modalityCodes: { anyOf: ["virtual"] } }, preferences: { dayParts: ["afternoon"] }, dateRange: { from: "2026-08-05", to: "2026-08-12" } }); const booking = await orita.confirmResolution( resolution.resolutionId, { optionId: resolution.options[0].optionId, customer: { name: "James Park", email: "james@example.com" } } );

{ "resolutionId": "res_7812", "status": "resolved", "expiresAt": "2026-08-01T14:07:00Z", "summary": { "providersScanned": 126, "eligibleProviders": 14, "providersWithAvailability": 4, "optionsReturned": 5 }, "options": [ { "optionId": "opt_92ab", "provider": { "id": "pro_82fa1", "displayName": "Dr. Ana García" }, "slot": { "start": "2026-08-05T15:00:00-04:00" }, "score": 94, "matchedConstraints": [ "service_supported", "language_match", "modality_match", "availability_valid" ], "reason": "Matches every required condition and is the earliest available afternoon appointment." } ], "exclusions": { "serviceNotSupported": 28, "notAcceptingNewClients": 12, "noAvailability": 22 }, "warnings": [] }

{ "id": "pro_82fa1", "organizationId": "org_123", "displayName": "Dr. Ana García", "professionCode": "clinical_psychologist", "languageCodes": ["es", "en"], "specialtyIds": ["anxiety", "cbt"], "modalityCodes": ["virtual"], "acceptsNewClients": true, "timezone": "America/New_York", "profileVersion": 12, "searchable": true }

{ "id": "evt_123", "type": "booking.confirmed", "createdAt": "2026-08-01T14:02:04Z", "organizationId": "org_123", "attempt": 1, "data": { "bookingId": "bk_18382", "resolutionId": "res_7812", "status": "confirmed" } }