Environments
Staging base URL, versioning and request conventions. Go to environments
Overview
Ordo is an event-sourced core system for savings-finance companies. This portal is for teams building integrations against the platform: REST API reference, core concepts and environment details live here. The platform’s technical codename is TFS — URLs, package names and repository names carry it; the product is Ordo.
Reference pages not yet translated are shown in Turkish with an automatic fallback notice.
Quick start
Section titled “Quick start”Authentication
OIDC on Keycloak: Authorization Code + PKCE and permission codes. Read about authentication
Error contract
messageCode, severity, traceId and the three-locale message catalog.
Read the error contract
API reference
From parties to lottery, deliveries to end-of-day. Go to the reference
Design system
Token tables, component inventory, layout patterns, mark and wordmark. Go to the design system
Technical presentation
A 33-slide technical deck from architecture to installation; presented from the browser, key required. Open the presentation
Shape of the API
Section titled “Shape of the API”- Base URL (staging):
https://tfs-api.karyabilisim.com - Versioning: Business endpoints live under
/api/v1/...; public endpoints under/api/public/.... - Format: JSON, UTF-8. Dates are ISO 8601, timestamps RFC 3339.
- Money: All amounts are integers in minor units (kuruş).
1250000= 12,500.00 TRY. - Compatibility: API contracts carry an N-5 minor-version backwards-compatibility commitment.
Design principles
Section titled “Design principles”- Derived values are never posted. Financing amounts, allocation scores and pool balances are computed by the platform; the API rejects them as input.
- Every response is traceable. All responses carry a
traceId— include it in support requests. - Rules are versioned. A contract’s math is computed with the rule-set versions pinned at establishment.