# API reference

Understand portal access, SDK transfer and the source-matched endpoint catalogue.

## Separate access surfaces

The Portal API manages definitions, review and comparisons using an authorised user session. SDK transfer uses service credentials and signed configuration. Do not substitute portal sessions for SDK credentials or vice versa.

The endpoint catalogue reflects routes mapped in the current product source. Examples do not connect to a live institution or request real credentials.

## Check the version

Use your institution’s GET /api/platform response to identify product and SDK versions, then match them to this reference. A path without a version number does not guarantee an unchanged contract across every release.

## Read-like actions with side effects

Some content-opening, evidence-download and verification routes use POST to enforce authorisation and record access. Do not convert them to GET arbitrarily. A read-like action can have an audit side effect.

## Explore endpoints

Search the [endpoint explorer](https://www.sigillum.cloud/developers/api/endpoints/) by method, path or purpose. Read [Authentication](https://www.sigillum.cloud/developers/api/authentication/) and [Errors](https://www.sigillum.cloud/developers/api/errors/) before integrating.