Step-by-step guides · Help Center
Connect your LMS, the API and webhooks
To stop issuing by hand: let the credential go out on its own when someone finishes a course.
Pick your path
- You use Moodle: the official plugin is the short road.
- You use Canvas, Blackboard, Brightspace or Sakai: LTI 1.3.
- You have your own system: the REST API.
- You want your system to hear about what happens here: webhooks.
Moodle
From then on, when a student meets the completion criteria, the credential issues and sends itself. Each issuance uses allowance exactly as if you had done it by hand.
- Download the plugin from Integrations and install it on your Moodle.
- Generate an API token in the panel and paste it into the plugin settings.
- In each course, choose which badge is issued on completion.
LTI 1.3
Integrations holds the four values any LTI platform asks for: the Issuer, the Client ID, the login URL and the redirect URL, plus the JWKS. They are configured once on your LMS side.
The API
Two endpoints cover the essentials. Both authenticate with a secret token you generate in the panel, shown only once.
- GET /api/v1/estado — returns your plan, your available credentials and when your cycle renews.
- POST /api/v1/emitir — takes the badge, name and email, and returns the signed credential.
Heads up: Check status before a large run. If you are about to issue 500 and have 80 left, better to learn it from the API than halfway through.
Webhooks
From the Institución plan your system can be notified whenever something relevant happens: a credential issued, claimed, revoked or restored.
- Register your URL under Integrations.
- Keep the secret we give you: every delivery is signed with it.
- Verify the signature before trusting the payload. That is the difference between a webhook and a form open to the world.
Sub-issuers
If your institution has faculties, campuses or schools that want to issue under their own identity, sub-issuers do exactly that within your umbrella: 3 on Institución, 25 on Red, unlimited on Enterprise.