CNTE Partner API

Developer Documentation v1

Base path /api/v1/partner · Contact developers@ciu.edu.lr

Authentication

Send your API key in the X-API-Key header. Keys are issued by CNTE administrators, are scope-limited, rate-limited, and can be rotated or revoked at any time.

curl -H "X-API-Key: cnte_pk_..." https://cnte.ciu.edu.lr/api/v1/partner/verify/CIU-GC-2026-0142

verify

Verify any CNTE document/credential code.

credentials

Retrieve normalized credential records and signed Open Badges 3.0 / VC 2.0 exports.

impact

Aggregated, non-identifying platform impact figures.

Per-key requests-per-minute limit (default 60). HTTP 429 on excess.

Endpoints

GET /api/v1/partner/verify/{code} scope: verify

Verify a credential/document code. Returns type, summary, and revocation status.

GET /api/v1/partner/credentials/{ctype}/{code} scope: credentials

GET /api/v1/partner/credentials/{ctype}/{code}/export?format=ob3|vc scope: credentials

Signed JSON-LD export. Designed to align with Open Badges 3.0 / W3C VC 2.0; conformance testing pending.

GET /api/v1/partner/impact/summary scope: impact

Aggregated platform statistics. No personal data.

Webhooks & signatures

Events: credential.status_changed, fhir.encounter.signed, fhir.observation.critical

X-CNTE-Signature: HMAC-SHA256 of the raw request body using your webhook secret.

Credential proof verification: Fetch the issuer public key at GET /api/credentials/issuer. Proofs are Ed25519 over JCS-canonicalized JSON (proof field excluded).

Versioning & deprecation: Breaking changes ship under a new version prefix (/api/v2/...). v1 endpoints receive a minimum 6-month deprecation notice via this documentation and webhook notice.

Data protection: Partner endpoints never return passwords, identity documents, private learner records, GPS histories, or unconsented evidence.

← Trust & Standards

Install CEPRES NTE

Add CEPRES to your home screen for faster access — works offline for status checks.