Developers

Reference · RxPhoto

RxPhoto API reference

Build on RxPhoto's clinical photography platform — patients, images, before/after pairs, galleries, and more. Most endpoints sit under /api/v3/ and exchange JSON. Browse the catalog below, then open any operation for its exact path, parameters, and examples.

ℹ️ Authentication

RxPhoto uses a single token header (Authorization: Token YOUR_TOKEN), obtained from an /api/v3/authenticate/… endpoint. See Authentication — RxPhoto for details.

📎 Looking for PatientNow Essentials?

This reference covers the RxPhoto API. If you need the PNE surface (customers, treatments, inventory, webhooks and more), see the PatientNow Essentials API reference →.

Conventions at a glance

Base URLhttps://api.rxphoto.com
PathsMost endpoints sit under /api/v3/…; check each operation for its exact path
AuthAuthorization: Token YOUR_TOKEN header on every request (details)
FormatPrimarily JSON (snake_case fields); some operations return files such as application/pdf
VerbsGET read · POST create · PUT/PATCH update (PATCH preferred) · DELETE remove
PagingResource-specific — some lists use page/page_size, others limit/offset; see each operation's parameters
IDsInteger IDs — use as returned

Resource catalog

All resources, grouped by area — loading…. Filter to find one fast.

No resources match that filter.


Operations

Every operation, grouped by resource. Examples omit the host for brevity — prepend your base URL. Field values in request and response examples are illustrative.