GRegistry — Postman collection

API collection for the Registrul Sistemelor Informaționale (RSI).

Files

• GRegistry.postman_collection.json — the collection (11 folders, 53 requests). Its built-in variables default to localhost, so it works out of the box against a local backend.
• GRegistry.server.postman_environment.json — an environment pointing at the deployed server (gregistry.gstack.esempla.systems + the real Keycloak realm interdictii).

Quick start (localhost)

1. Import the collection into Postman.
2. Start the backend (:8085) and Keycloak (:9080, realm jhipster).
3. Run 00 · Auth → Get Token (password grant) — creds admin / admin. It stores the access token in the {{token}} collection variable.
4. Call anything else — every request inherits Bearer {{token}} automatically.
5. 01 · Public needs no token.

Server

Import GRegistry.server.postman_environment.json and select it. Note: the gregistry-web client is public / PKCE with Direct Access Grants OFF, so the password-grant token step will likely fail against the server. Options:

• Use the public (no-auth) endpoints (folder 01) — they work anywhere.
• Or configure the collection’s Authorization → OAuth 2.0 (Authorization Code + PKCE, auth URL …/realms/interdictii/protocol/openid-connect/auth, token URL as in the env, client gregistry-web) and let Postman fetch the token interactively.

Zones

• /api/v1/public/** — anonymous consultation (ADR-006).
• /api/** — OIDC bearer (staff/admin).
• /management/** — ops (health/liveness/readiness/info are public).

Notes

• 09 · Registry Audit is read-only — the audit log is append-only (ADR-003), so there is no create/update/delete.
• Enum values are documented in each folder’s description.
• Create requests save the new entity id into a variable ({{systemId}}, {{providerId}}, …) so the get/update/delete/dependency requests chain off it — run Create first.