For Relying Parties
Docs · Issue
Send credentials into holder wallets via `POST /v1/credentials/issue` or the dashboard. This page covers API usage, bulk uploads, and revocation.
POST /v1/credentials/issue
Authorization: Bearer <ISSUER_TOKEN>
Content-Type: application/json
{
"credential_type": "staff_id",
"subject": { "email": "john@example.com", "name": "John Doe" },
"attributes": {
"employee_id": "EMP12345",
"department": "Engineering",
"access_levels": ["office", "lab"],
"end_date": "2026-12-31"
},
"presentation_methods": ["nfc", "qr"],
"metadata": { "internal_id": "hr_12345" }
}Response includes `credential_id`, `issuance_link`, and `qr_code`. Holders click the link or scan the QR to accept in their EUDI wallet.
email,name,employee_id,department,access_levels,end_date john@acme.com,John Doe,EMP12345,Engineering,"office,lab,parking",2026-12-31 jane@acme.com,Jane Smith,EMP12346,Sales,"office,parking",2026-06-30
Upload inside `/dashboard/issue` or call `/v1/credentials/bulk-issue`. Each row becomes a credential; Nexiel emails claim links to recipients.
POST /v1/credentials/{credential_id}/revoke updates status immediately and notifies holders.expires_at when issuing; Nexiel enforces expiry automatically./v1/nfc/verify to confirm the credential is still valid.Related guides