API

DAM API keys, endpoints and integration examples.

API key

Use this key as a bearer token. The full key is available to Print Clever admins and can be copied below.

Loading API key…
Rotate this key before giving access to third parties. For production, create per-integration keys with scopes and audit trails.

Authentication

Authorization: Bearer <API_KEY>
# or
x-api-key: <API_KEY>

All `/api/v1/*` routes require the API key. The existing browser app routes still use Microsoft/session auth.

Endpoints

GET
/api/v1/customers
List customer workspaces, asset counts, storage prefixes and contacts.
POST
/api/v1/customers
Create a customer workspace and Blob folder structure.
GET
/api/v1/assets?customerId=warhammer&status=UPLOADED&q=jersey
Search/list assets with optional customer, status and text filters.
POST
/api/v1/assets
Upload a new asset with multipart form fields: title, customerId, notes, file.
POST
/api/v1/assets/{id}/comments
Add an artwork comment. JSON body: { body, author? }.
POST
/api/v1/assets/{id}/version
Upload a new asset version with multipart fields: file, actor?.
PATCH
/api/v1/assets/{id}/status
Move an asset status. JSON body: { status, actor? }.
GET/PATCH
/api/v1/customers/{id}/notification-settings
Read/update customer notification toggles and recipient rules.
GET
/api/v1/customers/{id}/notification-events?type=status
Read recent logged notification events for UAT/audit.
GET
/api/assets/{id}/download?version=2
Download an authenticated app asset version. Browser/session auth currently, API-key version to follow.

Examples

curl -H "Authorization: Bearer <API_KEY>" \
  https://app-printclever-dam-prod-061314.azurewebsites.net/api/v1/assets
curl -X POST -H "Authorization: Bearer <API_KEY>" \
  -F "customerId=warhammer" \
  -F "title=New jersey front" \
  -F "notes=Uploaded from supplier API" \
  -F "file=@artwork.png" \
  https://app-printclever-dam-prod-061314.azurewebsites.net/api/v1/assets