ОUЯUKΛ / Changelog
DE EN

What changed.

All public versions of OURUKA — from the first API to today. Internal changes are not listed.

Version 2.3.1

Patch 2026-04-26
Changed
  • POST /v2/keyify now requires an X-API-KEY header — consistent with all other endpoints

Version 2.2.0

Minor Release 2026-04-26
Added
  • /v2/uid/numeric and /v2/uid/alpha now require an X-API-KEY header
  • POST /v2/schemas: Response now includes preview — a preview of the first ID without incrementing the counter
  • GET /v2/schemas: Each schema now includes preview, last_generated (last generated ID), and last_generated_at

Version 2.1.0

Minor Release 2026-04-25
Added
  • Mapping Tables — central lookup tables for attribute-based ID generation
  • New placeholder {MAP:tablename} in schema patterns — value is resolved from the table at runtime
  • Full CRUD endpoints for mapping tables: create, list, retrieve, delete
  • Plan-based limits for number of tables and entries per table
  • GET /v2/me now also shows mapping limits and current table count

Version 2.0.0

Major Release 2026-04-25
Added
  • Plan system: four tiers with defined limits — Discovery (Trial, 2 schemas, 2,000 IDs/month), Orbit (5 schemas, 10,000 IDs/month), Galaxy (15 schemas, 50,000 IDs/month), Universe (30 schemas, 150,000 IDs/month)
  • Monthly ID usage is tracked automatically; when a limit is exceeded, an upgrade suggestion is shown
  • GET /v2/me now returns plan limits and current usage

Version 1.5.0

Minor Release 2026-04-24
Added
  • Rate limiting for public endpoints: max. 60 requests per minute per IP address

Version 1.4.0

Minor Release 2026-04-24
Added
  • New schema type hash for deterministic content fingerprinting
  • Same input → always the same hash (SHA-256, configurable length: 16, 32, 40, or 64 characters)
  • Typical use case: duplicate detection during supplier or dataset onboarding
  • Hash IDs are stored in history like all other IDs — duplicates immediately visible

Version 1.3.0

Minor Release 2026-04-23
Added
  • {COUNTER:N:interval} — counter with automatic reset per period. Intervals: daily, monthly, quarterly, yearly. Example: {COUNTER:4:yearly} → resets to 0001 every year
  • Schema deletion now returns a summary: count of deleted history entries and counters
Changed
  • Internal database structure optimised for higher history stability
  • Background cleanup logic improved

Version 1.2.2

Patch 2026-04-20
Added
  • GET /v2/changelog — version history of the service retrievable as JSON
Changed
  • Schemas are immutable after creation. To change: delete the schema and recreate it
  • Security improvements in the authentication layer
Fixed
  • DELETE /v2/schemas/{name} now cleans up completely — history entries are also deleted

Version 1.2.1

Patch 2026-03-19
Added
  • UIDs: Allowed lengths extended to 256 and 512 characters
  • Swagger UI significantly expanded: endpoint descriptions, placeholder explanations, examples, and use cases added

Version 1.2.0

Minor Release 2026-03-12
Added
  • GET /health now returns the current service version
  • Background worker for automatic cleanup of expired data (interval: 12 hours)

Version 1.1.0

Minor Release 2026-02-25
Added
  • POST /v2/uid/numeric — cryptographically random numeric ID (lengths: 16, 32, 64, 128 characters)
  • POST /v2/uid/alpha — cryptographically random alphanumeric ID (a–z, A–Z, 0–9)
  • POST /v2/keyify — convert UTF-8 string to system-safe ASCII key (umlaut transliteration)

Version 1.0.0

Major Release 2026-02-25
Added
  • REST API for generating unique, rule-based IDs
  • Schema patterns with placeholders: {DATE:YYYY}, {DATE:MM}, {DATE:DD}, {COUNTER:N}, {VAR1}{VAR4}
  • ID history per schema (retrievable with timestamp)
  • Multi-tenancy: each API key gets an isolated workspace with its own schemas and counters
  • GET /health — system status with PostgreSQL and Redis check