Overview
Let third-party tools publish to portfolios and read library media on a photographer's behalf — OAuth, PAT, and `/api/v1` for Lightroom and custom integrators.
ArtInStack's Developer API lets third-party tools act on a photographer's behalf — publishing images to portfolios, reading library media — without going through the dashboard UI. This powers the official Lightroom Classic Publish Service, so photographers can export straight from their catalog to a portfolio, with retry-safe uploads and no manual re-upload step. The same OAuth/PAT contract is open to other integrators who want to build on top of a workspace's media and portfolios.
This is the tenant-scoped HTTP contract for those clients. It is not the anonymous storefront API (/api/public/…) and not the dashboard cookie session API (/api/… used by the logged-in UI).
Base URL
| Environment | API host |
|---|---|
| Production | https://app.artinstack.com |
Resource paths are under /api/v1/. OAuth protocol endpoints are under /oauth/authorize (page) and /api/oauth/token, /api/oauth/revoke.
Credentials
| Model | Use when |
|---|---|
| OAuth 2.0 + PKCE | Desktop/mobile apps where a user signs in and consents (Lightroom, partner apps) |
| Personal access token (PAT) | Scripts, CI, camera-trap pipelines, automation where OAuth is impractical |
Both resolve through one Bearer middleware on /api/v1/*. See Authentication.
v1 resources
Private beta focuses on the Lightroom publish path:
- Media — upload rendered JPEGs
- Portfolios — list destinations and attach media
Conservation resources (observations, surveys, deployments) ship in a later API phase.
API reference
Browse endpoints, auth, and request/response shapes in the interactive API reference.
Official clients
Download official binaries from Software. Setup walkthrough: Lightroom Classic.
Next steps
- OAuth 2.0 — authorize a public client with PKCE
- Scopes — required capabilities
- Media and Portfolios — upload and publish