Create API-Registry

[matKlju]

AS A Service-Module admin / service creator
I WANT a dedicated API Registry page
SO THAT I can centrally manage endpoints and clearly see test and schema readiness

---

---

Description

Create a dedicated API – Varamu / API – Registry page for centralized endpoint management.

The page is accessible from the sidebar:

• Teenused (Services) → API – Varamu / API – Registry

Core principle:

• Verification is non-blocking
• Endpoints can exist and be used without being tested
• Verification metadata is the source of truth

---

Specification

Header

• Title: API – Varamu / API – Registry
• CTA: Loo uus otspunkt / Create new endpoint (Endpoint Creation Modal - 928)

Search

• Otsi (Search) by endpoint name
• Case-insensitive

Table

• Columns:

  • Nimi (Name)
  • Viimane test (Last test)
  • Staatus (Status)
  • Skeem (Schema)
  • Tegevused (Actions)

• Sorting:

  • Nimi (Name) → A–Z / Z–A
  • Viimane test (Last test) → newest / oldest
  • Staatus (Status) → status, then name
  • Skeem (Schema) → has schema / no schema, then name

Row content

• Nimi (Name)

  • Displays endpoint name
  • Tooltip on hover

• Tooltips

  • On hover (Name column), show a popup with key endpoint details:
    • Meetod (Method) → GET / POST
    • URL (Endpoint URL) → full resolved URL
    • Tüüp (Type) → Custom / OpenAPI
    • Parameetrid (Parameters) → request params (if present)
    • Päised (Headers) → request headers (if present)
    • Keha (Body) → request body (if present)

• Display in a simple, readable format:

  • Rules:
    • Show only existing sections
    • Keep format readable and structured

ENDPOINT TYPE: Custom / OpenAPI
URL: [www.example.ee/this/that](http://www.example.ee/this/that)
METHOD: GET
PARAMETERS:
    param1_name : param1_value
        param1_type : STRING / DATE / NUMBER
HEADERS:
    header_name : header_value
BODY:
    {
       "field": "value"
    }

• Viimane test (Last test)

  • Shows latest test timestamp
  • If never tested → ---

• Staatus (Status)

  • verified → ✓ + 2xx (incl. 204)
  • failed → ⓧ + non-2xx
  • untested → ⓧ + ---

• Skeem (Schema)

  • Shows whether response schema has been captured

Schema logic

• No schema + failed test → no schema shown
• No schema + successful test → schema captured
• Existing schema + successful test → schema overwritten
• Existing schema + failed test → previous schema retained
• 204 → success, no schema returned → do NOT overwrite existing schema

Actions

• Kopeeri (Copy)

  • Creates a duplicate of the endpoint with base configuration
  • Resets verification state

• Testi (Test)

  • Executes endpoint test using stored configuration
  • Updates verification metadata and schema (on success)

• Muuda (Edit)

  • Opens endpoint configuration modal for editing (separate task to be added!)

• Kustuta (Delete)

  • Removes endpoint from registry
  • Requires confirmation

Confirmation modal:

---

Acceptance Criteria

• API Registry page is available in sidebar under Teenused → API – Varamu / API – Registry
• Header displays correct title and create CTA
• All visible labels use bilingual format (ET / EN)
• Search works by endpoint name, case-insensitive
• Table displays correct columns with translations
• Sorting works for all sortable columns
• Tooltip is available on Name column
• Tooltip displays method, URL, type, parameters, headers, and body
• Tooltip hides empty sections and maintains readable structure
• Last test shows timestamp or --- if never tested
• Status is shown correctly for verified, failed, and untested endpoints
• Schema state follows overwrite and retention rules
• Copy duplicates endpoint and resets verification state
• Test updates persisted verification metadata and schema correctly
• Edit opens endpoint modal
• Delete requires confirmation before removal
• Untested endpoints remain allowed and usable

[matKlju]

@1AhmedYasser NB! Remove the "Avalikkus/ Visibility" column - Service type will not be displayed!!!