Multi-Insurer API Integration Platform — UAE & KSA

The Problem

Shory needed to bring Motor, Health, and Travel insurance online across two markets fast — but each insurer used a completely different API structure: different authentication (API keys, OAuth, mutual TLS), inconsistent field naming, and error codes with no standard. Government integrations in UAE and KSA added regulatory schema requirements on top. Manual onboarding took weeks per partner, was error-prone, and had no repeatable validation process to catch failures before they reached production users.

Integration Architecture

Built a structured integration pipeline: translated raw partner specs (REST, SOAP, PDF) into normalised internal schemas, then ran every integration through a validation suite covering auth, payload structure, edge cases, and error handling before any partner went live. No integration reached production without passing the full validation suite.

Sample Integration Payload (sanitized)

{
  "request_id": "req_xK9mP2qL7nR",
  "insurer_code": "INS_[REDACTED]",
  "product": "MOTOR_COMPREHENSIVE",
  "applicant": {
    "id_type": "EMIRATES_ID",
    "dob": "1990-01-01",
    "nationality": "AE"
  },
  "vehicle": {
    "make": "Toyota",
    "model": "Camry",
    "year": 2021,
    "chassis_no": "[REDACTED]"
  }
}

// Validated: auth header, required fields, date format, enum values
// Expected: 200 OK with premium breakdown + quote_id

Business Impact

• 160+ API integrations across Motor, Health, and Travel — every one validated before production deployment
• 17 insurers onboarded end-to-end across UAE & KSA, and 7 government entities
• Reusable validation suites meant each new insurer onboarding re-used existing test coverage rather than starting from scratch
• Partner-facing integration guides allowed insurers to self-serve through the integration process with minimal back-and-forth