Minerva API

Permissions

Which API-key role each operation requires.

An API key carries one role. Roles are flat — admin does not implicitly satisfy an editor-only route — and an operation that needs a role your key does not have answers 403 with the code FORBIDDEN.

Operations not listed accept any valid key.

OperationRoles
POST /extractionsadmin, editor
PATCH /extractions/{id}admin, editor
DELETE /extractions/{id}admin
POST /extractions/{id}/documentsadmin, editor
POST /extractions/{id}/promoteadmin, editor
PATCH /extractions/{id}/validation/data-pointsadmin, editor
PATCH /extractions/{id}/validation/data-points/{dataPointId}admin, editor
POST /documentsadmin, editor
PATCH /documents/{id}admin, editor
PATCH /documents/metadataadmin, editor
DELETE /documents/{id}admin
POST /documents/processadmin, editor
POST /extraction-sessionsadmin, editor
PUT /data-groups/{id}/schemaadmin, editor
POST /jobs/{jobId}/canceladmin, editor
GET /api-keysadmin
POST /api-keysadmin
PATCH /api-keys/{id}admin
DELETE /api-keys/{id}admin
POST /api-keys/{id}/rotateadmin
GET /webhook-endpointsadmin
POST /webhook-endpointsadmin
GET /webhook-endpoints/{id}admin
PATCH /webhook-endpoints/{id}admin
DELETE /webhook-endpoints/{id}admin
POST /webhook-endpoints/{id}/rotateadmin
POST /webhook-endpoints/{id}/testadmin
GET /webhook-endpoints/{id}/deliveriesadmin, editor
POST /webhook-endpoints/{id}/deliveries/{deliveryId}/redeliveradmin