Catalogue API and PID resolver
How to read the services of the node programmatically and how persistent identifiers of services are resolved.
The catalogue exposes a public, read-only JSON API. It allows cross-origin requests, so it can be called directly from a browser.
Endpoints
| Request | Purpose |
|---|---|
GET https://sc.eosc.sk/api/v1/services` | List of production services (paged) |
GET https://sc.eosc.sk/api/v1/services/<urn:uuid>` | One service by its identifier |
GET https://sc.eosc.sk/resolve/<pid>` | Resolves the persistent identifier of a service to its record |
Parameters of the list: from, quantity (max 500), sort (name, createdAT, updatedAT, id), order (asc/desc), search, modifiedAfter (ISO 8601 timestamp).
## JSON Schema
https://sc.eosc.sk/api/v1/schema.json
Only services that are active and flagged for EOSC exposure are returned; prototypes stay internal.
The same records are what the EOSC Federation harvests from the node, and what the landing page renders in its Service Catalogue block.