Credentials can be issued by manually entering in the individual’s information or by using a bulk upload format such as a CSV or Tab-delimited Text (.txt) file. Once a credential is successfully issued to a user, they will receive an email notification letting them know they have received a new digital credential.
Best Practices for Manual Upload:
To include additional data on credentials such as credential numbers, expiration dates, course dates, etc, use the JSON Data section to manually input the information. Data must be entered in JSON format, an example is below:
{
“Credential Number”: “0553-92”,
“Expiration Date”: “05/01/2027”,
“Course Dates”: “April 26, 2025 – April 30, 2025”
}
- Deduplication – While optional, a unique identifier(s) allows for easy updating/editing of credentials and to prevent accidental duplication of credentials.
- In order to use the unique identifier the original data must be uploaded with the same unique identifier specified.
- If the same unique identifier field is not specified in the deduplication section in the original credential and newest credential, the existing credential will not be updated with the new information; instead, a new credential will be issued.
Best Practices for Bulk Upload Formats:
Comma-Separated Values (.CSV) files are required to include the following format:
Credential Name, First Name, Last Name, Email
Tab-delimited Text (.TXT) files should be in the following tabbed format:
Credential Name First Name Last Name Email
To include additional data on credentials such as credential numbers, expiration dates, course dates, etc, simply add an additional field after the email header.
- Credential Name – If issuing only one kind of credential, use this field to enter the Credential Name that will be used on all credentials.
- Credential Header Name – When issuing multiple types of credentials/certification names at a time, use this field to specify what Header name the fields are listed under in the file.
- Field Mapping – If data being uploaded includes different headers than what is required, use the mapping feature to specify which headers correlate with the required credential fields.
- Deduplication – While optional, a unique identifier(s) allows for easy updating/editing of credentials and to prevent accidental duplication of credentials.
- In order to use the unique identifier the original data must be uploaded with the same unique identifier specified.
- If the same unique identifier field is not specified in the deduplication section in the original upload and newest upload, an existing credential will not be updated with the new information; instead, a new credential will be issued.
After uploading credentials, you will receive immediate confirmation if the upload was successful and clarification if there were any credential issuing errors that need to be resolved and resubmitted within the data. Examples of such notifications are included in the scribe below.