iblai-api-credentiallisted

# iblai-api-credential Manage an organization's **digital credentials** from the API: create and edit credentials, assign them to users and groups, read the resulting assertions (issued credentials), import/export course-scoped credentials between platforms, wire up external issuing providers (e.g. Accredible) via provider config and per-credential external mappings, and pull issuance analytics over time. Use when issuing, assigning, importing, or reporting on digital credentials and certificates. ## Auth & conventions - **Base URL:** `https://api.iblai.app/dm` — these are Data Manager (DM) endpoints, so the **`/dm` prefix is required**; the `/api/credentials/…` paths below are appended to it (e.g. `https://api.iblai.app/dm/api/credentials/…`). - **Header:** `Authorization: Api-Token $IBLAI_API_KEY` on every request. - **Path vars:** `{org}` = `$IBLAI_ORG` (the credentials API path segment is `platform_key`; it resolves against `Platform.key`, with `Platform.org` as a fallback; on the wire it is also the `platform_org` query param). The user segment accepts **either** a numeric `{user_id}` **or** a `{username}` — both route shapes exist (`…/users/<int:user_id>/…` and `…/users/<str:username>/…`), so `$IBLAI_USERNAME` works directly in the path. For provider-config/mapping paths that user segment is the admin making the request (use `$IBLAI_USERNAME`). `{course_id}` = an Open edX course id such as `course-v1:org+course+run`. - **Most paths are user-scoped**