---
title: Introduction
description: Getting started with the Verifycate developer API
group: Guides
---

# Introduction

# Introduction

The Verifycate API lets you create certificates, import recipients, issue and send certificates, review request-form and correction submissions, and verify public certificates programmatically.

**Base URL:** `https://api.verifycate.com`  
**API prefix:** `/api/v1`

Authenticated workspace endpoints use a workspace API key (`Authorization: Bearer vc_...`). Public verification endpoints need no authentication.

## Where to start

1. Read the [Quickstart](/docs/api/quickstart) for your first authenticated request.
2. Create an API key in the dashboard at [app.verifycate.com](https://app.verifycate.com) (Workspace → API Keys). Keys are shown once and start with `vc_`.
3. Review [Authentication](/docs/api/authentication) and [Scopes](/docs/api/scopes).

## What you can do in v1

| Area | Examples |
| --- | --- |
| Certificates | Create, list, get, update, and delete certificates |
| Issues | Import recipients, issue and send, update, reissue, delete |
| Recipients | List and inspect recipients across a workspace |
| Request forms | List, approve, reject, and reopen submissions (uploaded files appear as short-lived URLs in list responses) |
| Corrections | List, approve, and reject correction requests (uploaded files appear as short-lived URLs in list responses) |
| Verify | Fetch a public certificate, check its signature, and download the Open Badge document |
| Webhooks | Receive signed HTTP callbacks for lifecycle and engagement events (Pro) |

Template draft, publish, and fork endpoints exist on the API but are not covered in this v1 reference. Recipient-facing form submit routes use portal session auth and are not part of this API-key reference.

## Conventions

- Paths are under `/api/v1`.
- JSON request and response bodies use `snake_case` field names.
- Errors use RFC 9457 `application/problem+json` — see [Errors](/docs/api/errors).
- Requests are rate limited; handle HTTP 429 and `Retry-After` — see [Rate limits](/docs/api/rate-limits).
- Say **Certificate** (not Credential) for the programme entity, and **Workspace** (not tenant or org) for the account.