canonical: https://jentic.com/apis/algeriacertify.com/algeriacertify

# Algeria Certify API

The Algeria Certify API issues, verifies, and manages trusted digital certificates for institutions. An institution issues a verified certificate, lists the certificates it has issued, and revokes one by id, while anyone can verify a certificate from its public token without a key. Dedicated Zapier triggers fire when a certificate is issued or revoked, and a Zapier action issues one, so the API drops into Zapier, Make, n8n, or any automation tool. A health check and an API-key validation endpoint round out the integration surface.

## For AI agents

Issue, list, verify, and revoke trusted digital certificates for an institution. Public verification needs no key, and built-in Zapier triggers and actions let an agent react to issuance and revocation events.

## Scope

Does not verify a person's identity, host documents for e-signature, or manage TLS or code-signing certificates. Use for issuing, verifying, and revoking trusted digital certificates only.

## Capabilities

- Issue a verified digital certificate for an institution
- List the certificates an institution has issued
- Revoke an issued certificate by its id
- Verify a certificate from its public token without any key
- Fire Zapier triggers when a certificate is issued or revoked, and issue one via a Zapier action
- Validate an API key and check service health before relying on it

## Use cases

### Agent-Issued Credentials on Completion

When a learner or applicant completes a program, an agent can issue a verified certificate through the institution endpoint and hand back a public verification token. Because verification is a public, keyless read, the recipient or a third party can confirm the certificate's authenticity from the token alone. This lets an agent close out a workflow by issuing a trusted, independently verifiable credential.

Example prompt: Issue a verified certificate for a named recipient through the institution endpoint, then confirm it by verifying the returned public token.

### Public Certificate Verification

An agent checking a credential presented by a candidate can verify it from its public token without holding any institution key. The public verification read returns whether the certificate is valid and current, so a hiring or admissions flow can confirm authenticity in a single call. This separates verification, which anyone can do, from issuance, which only the institution can.

Example prompt: Verify a presented certificate from its public token and report whether it is valid or has been revoked.

### Automating Issuance and Revocation Events

Because the API ships Zapier triggers for new and revoked certificates and a Zapier action to issue one, an agent can wire issuance and revocation into Zapier, Make, or n8n without custom polling. A trigger fires as certificates change state, and the action issues a certificate as a step in a larger flow. This makes certificate lifecycle events part of an automation rather than a manual task.

Example prompt: Subscribe to the new-certificate trigger, and when it fires, record the issued certificate's public verification token in a downstream system.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/institution/certificates` | Issue a verified certificate |
| GET | `/institution/issued-certificates` | List issued certificates |
| PATCH | `/institution/certificates/{id}/revoke` | Revoke a certificate by id |
| GET | `/public/verify/{token}` | Verify a certificate from its public token |
| POST | `/zapier/actions/issue-certificate` | Zapier action to issue a certificate |
| GET | `/zapier/triggers/new-certificate` | Zapier trigger for a newly issued certificate |
| GET | `/ping` | Health check |

## Key resources

- **Institution Certificates** — Issue a verified certificate, list issued certificates, and revoke a certificate by id
- **Public Verification** — Verify a certificate from its public token without a key
- **Zapier Integration** — Triggers for new and revoked certificates and an action to issue a certificate
- **Service and Keys** — A health check and an API-key validation endpoint for integration setup

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 44 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 74 / 100
- **View full report:** https://jentic.com/apis/algeriacertify.com/algeriacertify/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Algeria Certify API by hand means generating a Sanctum token in the Institution Dashboard, sending it as a bearer token on the institution operations, and keeping the public verification path keyless. Through Jentic you install once, import it from the API Directory, store the token once, and your agent issues, lists, and verifies certificates.
- **Permission scoping:** You choose which operations your agent may call, such as issuing and listing certificates, so revoking a certificate is not included unless you add it, and the public verification read needs no key at all. The certificate id travels in the revoke path (`/institution/certificates/{id}/revoke`), so a rule bounds which operations run.
- **Credential handling:** Your Algeria Certify Sanctum token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'issue a verified certificate' or 'verify a certificate token', and Jentic returns the matching Algeria Certify operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **BitBadges** — Blockchain-based verifiable badges and credentials rather than institution-issued digital certificates
- **BoldSign** — Legally binding e-signatures on documents instead of issuing and verifying standalone certificates
- **Onfido** — Verifies the identity of a person, complementing verification of the certificate they hold

## FAQ

### What authentication does the Algeria Certify API use?

Per its OpenAPI spec the Algeria Certify API uses an HTTP bearer scheme carrying a Sanctum API token, which you generate from the Institution Dashboard under API Keys and send in the Authorization header. The institution issue, list, and revoke operations require this token, while the public certificate verification and the health check need no key.

### Can I verify a certificate without an institution key?

Yes. The public verification operation takes a certificate's token and confirms whether it is valid or has been revoked, with no API key required. Issuing and revoking certificates, by contrast, require the institution's bearer token, so only the issuer can change a certificate's state.

### What are the rate limits for the Algeria Certify API?

The OpenAPI spec does not publish numeric rate limits for the Algeria Certify API. For current limits check the vendor documentation at https://algeriacertify.com.

### How do I issue a certificate with the Algeria Certify API through Jentic?

Import the Algeria Certify API from the Jentic API Directory, then have your agent search by intent such as 'issue a verified certificate' and Jentic returns the issue operation with its input schema. The agent issues the certificate and gets back a public verification token. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Can I limit what my agent is allowed to do with the Algeria Certify API?

Yes. Write a rule that allows only the issue and list operations, so your agent can create and read certificates but cannot revoke them, and the public verification read needs no key at all. The certificate id appears in the revoke path, so add the revoke operation only when the agent genuinely needs it, and every call it makes is logged.

### Is there an Algeria Certify MCP server?

You don't need an MCP server to give your agent the Algeria Certify API. Jentic connects it directly from the API Directory: import it, store your Sanctum token once, and your agent calls the issue, list, revoke, and verify operations on demand without loading another server's tool definitions into its context.

### Does the Algeria Certify API work with Zapier, Make, and n8n?

Yes. The API exposes Zapier-shaped triggers for new and revoked certificates and a Zapier action to issue one, plus an auth-test endpoint to validate the key. These let it slot into Zapier, Make, n8n, or any automation tool that speaks those patterns.