Bulk issuance by CSV
Award a whole cohort at once: the template, every column, and what happens when a row fails.
Open a badge, and in Issue this badge switch to the Bulk (CSV) tab. Choose a CSV file and you get a preview first: each row is marked Ready or shows why it will be skipped, and nothing is issued or emailed yet. Review it, tick or untick Email each recipient a link to their badge, then choose the Issue button (it shows the count, such as Issue 40 badges) to award every ready row. Keep the page open while it runs.
Start from the blank template
Download it from the bulk tab, or directly at /api/csv-template. It has the exact column headers in the right order, which removes the most common cause of a failed import.
Columns
| Column | Required | What it does |
|---|---|---|
email | Yes | Recipient's email address. Must be a valid address; it's lowercased and used to detect duplicates. |
name | No | Recipient's name, shown on the claim page and in the email greeting. |
valid_until | No | The last day the award is valid, as YYYY-MM-DD (the header expires also works). Blank uses the badge's default validity, or no expiry if it has none. A date that is not real, not later than today, or more than 50 years ahead fails that row. It cannot be changed after the award is issued. |
evidence_url | No | A link to evidence for this recipient. |
evidence_name | No | A short label for that evidence item. |
evidence_description | No | A sentence describing it. |
evidence_text | No | Longer context — what the recipient actually did. |
evidence2_url | No | A second evidence item, same idea. |
evidence2_name | No | Label for the second item. |
evidence2_description | No | Description for the second item. |
evidence2_text | No | Longer context for the second item. |
From a registration or event export
You don't need to rebuild your file. Rename the address column to email and the name column to name (capitalisation and stray spaces at either end of a header don't matter; the header must still be exactly email or name), and leave everything else: columns Incredify doesn't recognise are ignored. A file with only an email column works.
From an LMS gradebook or roster
The address column must be headed email. Canvas's Class Roster report (Course Analytics, Reports) can include addresses, depending on your institution's settings. Brightspace exports each learner's internal email address by default. Blackboard's documented gradebook download lists no address column. Steps for each system are in Issuing badges from an LMS course.
Two evidence slots, and no file uploads
CSV supports up to two link/text evidence items per row. Uploaded files can only be attached on the Recipients tab. If a cohort needs file evidence, add those people there instead (up to 25 at a time).
Limits and failures
- 1,000 rows per upload. Split larger cohorts across several files.
- Rows are processed independently. One bad row doesn't stop the run — the rest still issue.
- Problems are reported per row with the reason, so you can fix just those and re-upload. The preview flags a malformed email, a
valid_untildate that is not valid, a repeat of an earlier row in the same file, and a recipient who already holds the badge; a row can also fail while issuing. - Re-uploading is safe. Anyone who already holds an active award is skipped as a duplicate rather than issued twice.
- Addresses use plain letters. An address with accented or non-Latin characters (for example
josé@…orname@münchen.de) is flagged as malformed. Names are not restricted: accents and other scripts are kept as typed. For an internationalised domain, use its ASCII form (xn--…).
Check your headroom first
A bulk run stops when it reaches your plan's yearly limit. The rows already issued stay issued, and the result tells you how many were not attempted because the plan limit was reached, so you know exactly who is left. Your usage and limit are shown at the top of the Badges page.
Related
Still stuck?
Email us at hello@incredify.net — a human will answer.