Start building
Getting Started
Set up your credentials, exchange them for a token, and make your first API call in minutes.
Start here →Authentication
OAuth 2.0 Client Credentials flow — scopes, token TTLs, and how to rotate secrets safely.
Read the guide →Using the API
Request and response format, error codes, pagination, data model, versioning, and audit compliance.
Browse guides →Start Building
Task-oriented walkthroughs — create a study, export the hierarchy, ingest and transfer whole-slide images.
Follow a guide →Study API Reference
Interactive, try-it-live reference for every study endpoint — subjects, organs, slides, findings, and more.
Explore endpoints →Cloud Image API
Move whole-slide images between cloud buckets without a local machine. Credential management, ingest and transfer jobs.
Explore endpoints →What you can build
Automate study registration from your LIMS
Push subjects, organs, and study metadata directly from your lab information system — no manual data entry, no transcription errors.
Sync pathology data with your reporting pipeline
Pull findings and scoring data into your downstream analytics or regulatory submission pipeline programmatically.
Connect Patholytix to your sponsor dashboard
Surface study status, findings, and audit trails in your own portal — using the same compliant data your pathologists work in.
Up and running in 3 steps
Contact your Deciphex account representative to receive a client_id and client_secret.
curl -X POST https://api.account.dev2.patholytix.com/oauth2/token \ -d "grant_type=client_credentials" \ -d "client_id=YOUR_ID" \ -d "client_secret=YOUR_SECRET"
curl -X POST https://api.dev2.patholytix.com/api/v1/studies \
-H "Authorization: Bearer <token>" \
-H "Content-Type: application/json" \
-d '{"studyName":"My First Study","siteId":"YOUR_SITE_ID"}'Built for regulated science
Built for regulated environments
Every write operation produces an audit log entry attributable to your integration client — no operation goes unrecorded. Designed for GLP-regulated environments.
Scope-based access control
Fine-grained OAuth 2.0 scopes (Study:Read, Study:Write, Finding:Read) mean your integration gets exactly the access it needs — nothing more.
OpenAPI-first
Every endpoint is defined in an OpenAPI 3.1 spec. Generate a typed client in any language using OpenAPI Generator or Kiota.
Ready to integrate?
Explore endpoints live in the API Reference, or generate a client in your language from the OpenAPI spec.
Contact your Deciphex account representative to get a client_id and client_secret.
Try every endpoint live in the interactive API Reference — no setup required.
Track deprecations and new endpoints in the Changelog.