API References

API overview

The OrySense API lets you send conversations into OrySense and read results — scores, records and alerts — back into your own systems. API access is enabled per enterprise during onboarding.

Area	What it does
Ingestion	Submit recordings and their metadata
Results	Read ORY Scores, records and SOP checks
Alerts	Receive Red SOS events
Organisation	Sync stores, teams and users

Authentication

Every request is authenticated with a bearer token issued for your enterprise. Send it in the Authorization header:

Authorization: Bearer <your-access-token>

Tokens are scoped to your enterprise; data from other tenants is never accessible.

Ingestion

Recordings can be pushed by your systems or collected by the OrySense client-side server from your dialer or PBX. Each recording carries metadata that places it in your hierarchy:

{
  "external_id": "call-2026-10-14-00421",
  "store_id": "STORE-014",
  "agent_id": "AGT-2291",
  "channel": "phone",
  "started_at": "2026-10-14T11:02:51+05:30",
  "audio_url": "<signed upload URL>"
}

Processing is asynchronous: the recording is queued as soon as it arrives.

Results

When processing finishes, each conversation has a structured result:

{
  "external_id": "call-2026-10-14-00421",
  "eligible": true,
  "ory_score": 812,
  "dimensions": {
    "conversation_quality": 86,
    "product_knowledge": 78,
    "empathy": 91,
    "pitch_efficiency": 74
  },
  "intent": "Finance a premium smartphone",
  "objections": ["Competitor offers a lower rate"],
  "resolution": "Visit booked for Saturday",
  "red_sos": false
}

Field names shown are illustrative; your onboarding pack includes the full schema for your enterprise.

Callbacks

Instead of polling, register a callback URL to be notified when a conversation finishes processing or when a Red SOS is raised. Callbacks are signed so you can verify they came from OrySense.

Getting API access

API credentials, the full endpoint reference and sandbox access are provided to customers during onboarding.