Projects

A project is the container for one integration workload. Everything you configure - webhook endpoints, sync jobs, connections - lives inside a project, and every API call resolves to one.

Anatomy of a project

{
  "id": "prj_9kLm2xVb7nQe",
  "object": "project",
  "name": "billing-sync",
  "region": "us-east",
  "environment": "test",
  "status": "active",
  "created_at": "2026-08-14T09:31:07Z",
  "updated_at": "2026-09-02T14:12:44Z"
}

Choosing a region

Region determines where project data is stored and processed. Pick the region closest to your infrastructure or required by data-residency policy. Because region is immutable, changing it means creating a new project and migrating configuration.

Quotas

Quotas apply per project per environment:

Higher live limits are available on paid plans - see Production setup.

Naming conventions

• Use lowercase, hyphenated names that describe the workload: billing-sync, slack-alerts, warehouse-export.
• Names must be unique within a workspace - reused names make log correlation and support harder.
• The name appears in event payloads and delivery logs, so avoid embedding secrets or environment names.

Lifecycle

Projects move through three states:

1. active - normal operation.
2. suspended - reads work, writes and deliveries pause. Triggered by quota abuse or manually from the dashboard.
3. archived - soft-deleted. Configuration is retained for 30 days, then purged. Archived projects serve 404 on all endpoints.

curl -X DELETE https://api.meridian.dev/v2/projects/prj_9kLm2xVb7nQe \
  -H "Authorization: Bearer $MERIDIAN_API_KEY"

Archiving is reversible for 30 days via POST /projects/:id/restore. After that, deletion is permanent and IDs are never reused.

API reference

The projects resource exposes the standard five operations: list, create, get, update, and delete.