Integration Guide
Last updated
Last updated
This is the expected user flow for third party platforms looking to integrate OCAs into their ecosystem. At this moment, OCAs can only be issued to an OCID account, therefore it is important that the OCID Connect portion is set up on your platform before any issuance happens.
Reach out to @kittyvo_ or @lewlian on telegram to set up your developer account. Please provide some context on your project and more importantly the following fields:
OCID
Account Name
Company
When you have completed the integration on production, you should have a “Connect with OCID” that allows you to:
Create a new OCID
Login and connect an existing OCID
Before you move on to the next segment, it is recommended that you generate two OCID accounts:
Issuer’s OCID: This is the OCID account that will be requesting for Issuer permission and also become the Issuing entity for OCAs later. This should be the OCID that already has access to the developer portal
User’s OCID: This is the OCID account that will be receiving the OCA and view them on the OCID Dashboard.
Authorization
Once your obtained an API Key from our team, you will use your API Key in the HTTP POST header for authorization:
Staging endpoint for OCA Issuance:
Body Params (JSON)
Sample Body (raw JSON):
credentialPayload
object
holderOcId
string
bob.edu
OCID Dashboard
Once you have successfully issued the OCA to a holder’s OCID, there are two ways that you can view the OCA:
View the holder’s public profile at https://id.sandbox.opencampus.xyz/public/credentials?username=<OC_ID>
In order to ensure that third party integrations are successful and did not deviate too much from the intended flow of how OCAs should be issued, we require teams to do a recording of their integrated flow on the sandbox environment and submit to the Open Campus team via this form in step 3
To promote the sandbox environment to production, you will need:
Request for Issuer’s production API Key
Once this is approved, someone from the Open Campus team will reach out and provide you with your Production API key
Then replace with the production issuance endpoint
Secure your API Key safely, your API Key is tied to your issuer identity and losing your API Key means allowing others to issue Achievements on your behalf.
We have just launched the OC Developer portal hoping to scale up the capability of self-served integration for developers and partners. Head to to create an OCID if you have not already done so.
We will inform you once we have set up your developer account and you will be able to access the developer portal at
A sandbox environment can be activated in the SDK for development purposes. Please find the full guide for Open Campus ID Connect integration
Update: You no longer require a sandbox OCID to test the staging endpoint. You can use your actual production OCID for both staging and production OCA testing. Make sure you have a valid OCID from
On a high level, a Sandbox Issuer’s API Key will be needed to issue an OCA with the sandbox API endpoint provided. To obtain it, please complete this providing your issuer OCID and the Open Campus team will reach out to you on telegram.
If you have followed the , holderOcId will refer to the User’s OCID that you generated in the previous segment. If you only have one OCID generated you may also issue an OCA to the issuer’s account.
If you wish to find out more about the specifications for each of the properties in the body params, please refer to . You will also find the recommended image dimensions for OCAs there.
Logging in to the Open Campus ID Dashboard in the sandbox environment using the holder’s account at
Complete and submit this to the Open Campus team