HN Showcase
Back to browse
GitHub Repository

UAE Open Finance Insurance APIs Only Testing Backend - FAPI 2.0 compliant

2 starsJavaScript

Open Finance Insurance sandbox (OAuth2, quotes → policies)

by Renjit·Apr 16, 2026·3 points·0 comments
Visit ProjectView on HN

AI Analysis

●●SolidNiche GemSolve My Problem

FAPI-compliant insurance API mock with consent→quote→policy workflows for UAE market.

Strengths
  • •Full OAuth2 FAPI-compliant authentication with JWT tokens and header validation.
  • •Seven insurance types with realistic quote generation and policy conversion.
  • •Docker containerization with interactive Swagger documentation for easy testing.
Weaknesses
  • •UAE-specific implementation limits usefulness for global fintech developers.
  • •Testing backend only, not production infrastructure for actual deployments.
Category
Finance
Target Audience

Fintech developers integrating with Open Finance and insurance APIs

Similar To

Plaid Sandbox · Stripe Test Mode · TrueLayer Sandbox

Post Description

Most “Open Finance” repos stop at account aggregation. But when you try building against insurance APIs, you hit gaps fast: no real quote workflows, no consent flows, and no FAPI-compliant auth. So I built a UAE Open Finance Insurance testing backend.

It simulates the full lifecycle: OAuth2 FAPI-style authentication (JWT) Consent creation and authorization Quote generation across 7 insurance types Quote → policy conversion Webhook events and error handling Example flow: create consent → generate quote → accept → issue policy. It’s Dockerized, has Swagger docs, and is designed to mimic how a real TPP would integrate. This is a testing backend, not production infra. Curious what others found hardest when integrating Open Banking / Insurance APIs.

Similar Projects

Finance●Mid

Stockdata.dev – Free stock market API with 15-min delayed US quotes

Parses messy SEC XBRL into a simple REST surface — income statements, balance sheets, cash flow, filings with direct EDGAR links, plus insider trades and 13F holdings. The docs are clear (curl examples, param details, sample JSON) and the free 1,000-call tier makes it easy to prototype. Missing clarity on coverage, update cadence, and paid-tier limits keeps this from feeling like a must-have API for production at scale.

Niche GemSolve My Problem
jsandfort
233mo ago