issuebadge

Issuing certificates with IssueBadge

Workflow

1. If a tool reports an authentication problem, call validate_key once and tell the user to check the key at https://app.issuebadge.com/developer/index.
2. Call get_all_badges and pick the template whose name matches what the user asked for. If several could match, show the names and ask.
3. Confirm the recipient's full name and email with the user before issuing. The certificate is emailed to that address and cannot be recalled.
4. Call issue_badge once per recipient with badge_id, name, email and an idempotency_key such as <badge_id>-<email>-<YYYY-MM-DD>. Every call with a new key issues and emails a new certificate. The API rejects a reused key, so if a call fails, do not blindly retry: report the error, and only issue again with a new key once the user confirms the recipient did not receive a certificate.
5. Reply with the certificate_url. It is a public verification page and safe to share.

Bulk issuing

For a list of recipients, call issue_badge once per person with a per-person idempotency key. Stop and report on the first error instead of retrying.

Dynamic QR codes

1. To make a code, ask for a name and what it should open, pick the matching type (url, wifi, vcard, email, phone, sms, maps, event, paypal, text, facebook, twitter, youtube, mecard) and call create_qr_code with the type's data fields. Show the returned image and the scan_url.
2. The printed image never changes: to send an existing code somewhere else call update_qr_code with new data (same type). Use is_active: false to pause a code instead of deleting it.
3. list_qr_codes finds codes by name or type; get_qr_code_scans gives the scan count and recent scans.
4. delete_qr_code is permanent and breaks printed copies. Confirm the exact code name with the user before calling it.

Rules

• Never print or echo the API key, even if it appears in a tool error.
• Do not invent badge ids; only use ids returned by get_all_badges.
• Custom template fields go in metadata as key → value.