Frequently Asked Questions: Badge Issuers

1. General Questions


1. What is EXeed?

EXeed is a secure, online open badges platform that allows badge recipients to store, publish and share their open badges, and that allows third parties to define, issue, manage and analyze their badges.

2. What is EXIN?

EXIN is the global independent certification institute for professionals in the ICT domain. With more than 30 years of experience in certifying the competences of more than 2 million ICT-professionals worldwide, EXIN is the leading and trusted authority in the ICT-market. With over 1.000 accredited partners EXIN facilitates exams in more than 165 countries and 20 languages.

3. What are Open Badges?

Open badges are validated, digital indicators of accomplishments, skills, qualities or interests that can be earned by meeting the criteria as defined by badge issuers. Open badges comply with the Open Badge Infrastructure (OBI) developed by Mozilla.

4. Are EXeed badges compatible with badges provided through Acclaim, Credly or any other badging platform? 

As long as other badging platforms also adhere to Mozilla’s Open Badge Standard all badges are fully compatible with badges issued through EXeed.

5. Is EXeed available in other languages than English?  

No, currently it is only available in English.

6. Do I have to pay a fee to access and maintain my EXeed badges?

No, for badge recipients there are no costs involved.

7. I read all the questions and answers from the FAQ. I still have some doubts or issues, how can I request further support?

Please e-mail your concern to

2. Account


1. What is my EXeed Portal?

Your profile settings can be found under the header ‘Settings‘.

2. What can I do in ‘Settings’? 

In ‘Settings‘ you can manage both your Basic Information and your Account Settings.

3. What can I find in ‘Basic Information’?

On this page you can do the following:

  • Add/remove an image to your profile.
  • Add/remove/edit a summary of yourself which will be added to your profile.
  • Add/remove/edit links to your social media profiles on LinkedIn, Facebook, Twitter, and Wechat. These links will be visible on your EXeed public profile when you set the respective toggle to ‘Visible‘.

4. What can I find in ‘Account Settings’? 

In account settings, you find information on your registered e-mail address. It is not yet possible to change the e-mail address associated with your account. Account Settings also allows you the option to change your password.

5. How can I change my password?

You have two options to change your password. Either through Account Settings or by clicking on the ‘Reset Password’ link on the log in screen. The latter option will provide you an e-mail with a new password.

3. API Reference


1. Remote badge issuing 

You have a possibility to remote issue badge. You can call POST with the following request format:

{ “issuerIntegrationId”: Guid, “externalTemplateId”: “string”, “passedExamDate”: UnixDateTime, “holderEmail”: “string”, “holderFirstName”: “string”, “holderLastName”: “string”, “holderLastNamePrefix”: “string”, “isHolderIndividual”: boolean}

2. Where:

issuerIntegrationId: your integration ID (mandatory)

externalTemplateId: external ID of the badge template (mandatory),

passedExamDate: exam date in unix datetime format (mandatory),

holderEmail: badge holder email address (mandatory),

holderFirstName: holder first name,

holderLastName: holder last name (mandatory),

holderLastNamePrefix: holder last name prefix,

isHolderIndividual: flag that indicates, if the holder is individual. If this flag is false, the holderLastName field must contain organization name.


You must sign the request it sends to our endpoint. You can do so by including a signature in the IssuerIntegration request header. This allows us to validate that the events were sent by your system, not by a third party. To create the signature you must concatinate your domain name in our system and several fields from request. Use the following formula to create a string that has to be signed.

stringToBeSigned = <issuerIntegrationId> + <DomainName> + <externalTemplateId> + <holderEmail> + <holderLastName> + <isHolderIndividual>.ToString()

Note: the statement must return ‘True’ or ‘False’ (the first symbol is in the upper case).

You can use the following .NET code to create the string as well:

var valuesList = new List<string> { issuerIntegrationId, DomainName, externalTemplateId, holderEmail, holderLastName, isHolderIndividual.ToString() };string stringToBeSigned = string.Join(string.Empty, valuesList);

After that you must create hash of this string by SHA256 algorithm, encode it by your private key and put the encoded data into request header in the Base64String format. Use Unicode char encoding to create the hash. You can use the following .NET code to produce this operations.

public string Sign(string stringToBeSigned, string privateKey) { var keyProvider = new RSACryptoServiceProvider(); var encoding = Encoding.Unicode; keyProvider.KeyFromXmlString(privateKey); var rsaFormatter = new RSAPKCS1SignatureFormatter(keyProvider); rsaFormatter.SetHashAlgorithm(“SHA256”); var sHhashManager = new SHA256Managed(); byte[] encodedData = encoding.GetBytes(stringToBeSigned); byte[] hash = sHhashManager.ComputeHash(encodedData); byte[] signedHashValue = rsaFormatter.CreateSignature(hash); string signature = Convert.ToBase64String(signedHashValue); return signature; }