Developers

From API key
to first score

Partner registration → key issuance → first sandbox query → go live. Standard REST, signed responses, retried webhooks, SDKs in 4 languages.

FI API docsSwagger UIVerifier SDK

Quickstart

Integrated in four steps

  1. Register as a partner · get keys

    Get your Client ID and API key from the partner portal. Sandbox keys are self-issued.

  2. Check with whoami

    Confirm your key and scopes with GET /fi/whoami.

  3. First sandbox score query

    Preview responses for each tier using fixed practice subjects and fixed verification cases.

  4. Go live

    Pass the checklist, and the same code connects to production.

5-minute integration

A single call

# Consent-gated soft-pull score (deny-by-default)
curl -X POST https://trendy.storydot.kr/superapp/api/fi/score/query \
  -H "X-Client-Id: $CLIENT_ID" -H "X-API-Key: $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"pairwiseSub":"pairwise-subject-id","purpose":"LOAN_UNDERWRITING"}'
# → { success, data: { score, tier, reasonCodes[…] } } · every query is audit-logged

Partner API

Core endpoints

Base URL https://trendy.storydot.kr/superapp/api · header authentication X-Client-Id + X-API-Key · 60 requests per minute.

MethodPathDescription
POST/fi/score/queryConsent-based score query — score · tier · reason codes
POST/fi/decision/evaluateDecision evaluation against underwriting criteria
POST/fi/score/batchBatch query, 1~100 subjects
POST/fi/verifyVerify a presented credential
POST/api/v1/fi/proof/verifyZero-knowledge tier proof verification (scope proof:verify)
GET/fi/score/historyScore history, up to 365 days
POST/fi/consent/requestsCreate a consent request
GET/fi/consent/{id}Get consent status
GET/fi/usageUsage, up to 92 days
GET/fi/whoami · /fi/healthKey check · health check

Built for production

Designed for production

Webhooks

Signed and retried

4 event types. X-HACS-Signature HMAC-SHA256 signatures, with retries at 1 min · 5 min · 30 min · 2 h on failure.

Sandbox

A deterministic test environment

Fixed practice subjects, fixed verification cases and per-tier responses let you test even the edge cases in advance.

Recipes

Tier cut-off recipes

750 / 650 / 550 / 450 tier cut-offs, a reference table of lending terms by risk group, and example underwriting flows.

Errors

Reason codes vs. errors

An error-code table and HTTP status rules that clearly separate retryable errors from decision reasons.

Issuers

Issuer API

Application → review → approval → issuance in the institution’s name. A fail-closed issuance path.

Compliance

Every decision auditable

Consent controls, hash-chained access logs, model governance, decision provenance, identifier minimization.

SDKs

In the language you already use

LanguagePackageVersion
TypeScript · JavaScript@superwallet/verifier-sdk (npm)2.3.0
TypeScript · ZK@superwallet/zk-kit (npm) — 21 production circuit IDs0.2.0
Java 17com.superwallet (Gradle)1.1.0
Pythonsuperwallet-verifier1.1.0
PHP 8.1+superwallet/verifier-sdk (Composer)—