Docs

Integrate with Collecta partner workflows

Collecta is the operating system for serious art collections. Invited galleries, dealers, advisors, and service firms can connect collector-led workflows using OAuth 2.1 and REST APIs. Private preview.

Preview scope

The partner API is intentionally narrow: artworks, order operations, certificates, inventory sync, usage, and webhook subscriptions. It is not a public marketplace API.

Legacy optical and kiosk surfaces are excluded from this preview.

Authentication

Collecta uses OAuth 2.1 with PKCE for secure partner authentication.

Step 1 · Register as OAuth Client

Contact Collecta to register your application. You will receive a client_id and client_secret.

Step 2 · Redirect to Authorization

Send users to the Supabase authorization endpoint with your client_id, redirect_uri, and requested scopes.

Step 3 · User Grants Consent

Users see the Collecta consent page and approve access to their collector-linked partner data.

Step 4 · Exchange Code for Token

Your server exchanges the authorization code for access and refresh tokens.

Step 5 · Call Partner API

Include the access token in the Authorization header: Bearer <token>

Available scopes

openid

Verify user identity

email

Access user email address

profile

Access user profile information

API endpoints

All endpoints require a valid OAuth access token.

GET/api/v1/partner/artworksRetired

List Artworks

Retired. This endpoint predates the gallery schema and always answers 410 Gone. A replacement scoped to the current artworks data model is planned; contact Collecta for status.

GET/api/v1/partner/orders

List Orders

Fetch collector-originated orders for the authorized partner workspace. Supports pagination and filtering by status or date.

limit · offset · status · since

GET/api/v1/partner/orders/{orderId}

Get Order Details

Fetch full details for a specific order including artwork context, certificate data, and payment details.

PATCH/api/v1/partner/orders/{orderId}

Update Order Status

Update order status for fulfillment tracking. Valid statuses: pending, in_progress, completed, shipped, cancelled. Triggers webhooks.

GET/api/v1/partner/certificates

List Certificates

Fetch provenance and certificate data from partner-facing orders. Includes artwork details and dimensions.

limit · offset · order_id · since

POST/api/v1/partner/inventory

Sync Inventory

Update availability, stock quantities, and prices using the current partner sync surface. This endpoint retains legacy item identifier support for compatibility.

GET/api/v1/partner/webhooks

List Webhooks

List your webhook subscriptions and their delivery status.

POST/api/v1/partner/webhooks

Create Webhook

Create a new webhook subscription. Returns a secret for HMAC signature verification (shown once).

PATCH/api/v1/partner/webhooks/{webhookId}

Update Webhook

Update webhook URL, events, or enabled status.

DELETE/api/v1/partner/webhooks/{webhookId}

Delete Webhook

Delete a webhook subscription.

Webhooks

Receive real-time notifications when events occur.

order.created

Fired when a collector workflow creates a new partner-facing order

order.status_changed

Fired when fulfillment status changes

order.completed

Fired when an order is marked complete

inventory.updated

Fired when partner inventory sync writes compatibility updates

Webhook security

  • All webhooks are sent over HTTPS only
  • Each payload is signed with HMAC-SHA256 using your webhook secret
  • Verify the X-Webhook-Signature header matches your computed signature
  • Use the X-Webhook-Id header for idempotency

Example request

curl -X GET "https://collectapro.com/api/v1/partner/orders?limit=10" \
  -H "Authorization: Bearer <access_token>" \
  -H "Content-Type: application/json"

Ready to integrate?

Contact us to request invited access and receive OAuth credentials.

Request preview access

View core API reference