Updated 4/19/23
You can now replace credentials upon issuance using the bulk upload tool or API.
-
Note: This behavior only happens for templates where Duplicates setting = No (otherwise duplicates are issued as normal).
How to use it:
Bulk Issue
-
Create your csv as normal, including any data you'd want to update for an existing badge. Of course, the data for that badge has to MATCH an existing badge so our system sees it as a duplicate.
-
Upload csv.
-
View the new Badge Options - 'Replaces badges on detection of a duplicate badge.' is checked on by default.
-
Complete bulk issuing as normal.
via API
- Add new “duplicate_behavior”: “replace/allow/deny” in payload
| Template Duplicate Setting | API duplicate flag | Result |
| No | Replace | Replaces the badge with new one |
| No | Allow | Create a duplicate badge |
| No | Deny | Error message display |
FAQs
What constitutes a Duplicate?
How we define duplicates has not changed - so anything that would have previously triggered in error. For instance:
-
same email + same template id => yes that’s a duplicate
-
same issuer earner id + same template id => yes that’s a duplicate
What happens if there is a record that is exactly identical?
The Credly system will simply pass over any identical records. No changes will be made to identical badges.
What can be updated this way?
This is also exactly the same as how current Replace works - we update all the data you’ve included in your spreadsheet or API call:
-
Name
- Email (if issuer earner id and template id remain the same, AND badge state = pending)
-
Expires at
-
Group Tag
-
Country/ State
- Issuer Earner ID (if the email and template id remain the same)
-
Evidence
Notes:
- Issued at date will NOT be updated using this process.
- If optional fields (e.g. Issuer Earner ID) are included in the original badge issuance data and are not included in the re-issuance data, the badge will be updated to remove the data that was originally included in the badge.