Eye Cloud Pro API Documentation

Generated directly from the running platform — always current with what is deployed. Authenticate with your client credentials and try every endpoint live, right from these pages.

Open the API Reference Get an access token

Which API is which?

Current — use this

API v2

The Eye Cloud Pro platform API and the standard for all new integrations: patients, appointments, invoices, orders, inventory, pricebooks, and more. OAuth2 client-credentials authentication, JSON, fully documented here with live testing.

Browse the v2 reference →
Legacy — migrating into v2

API v1

nightly reports

If your practice pulls scheduled reports by requesting a web address with your report name and credentials — usually a nightly automated download — that is API v1. It keeps working for existing setups, but it's being retired into API v2: new automation should use v2, and we'll help plan your migration when you're ready.

Open the v1 report runner →
Legacy — migrating into v2

API MOSCOT

nightly reports

Invoice and daily-close reporting endpoints, also included as its own section of the v2 reference. Its capabilities are being folded into API v2 — new reporting integrations should discuss timelines with us before building.

Open the MOSCOT docs →

Getting started

Integration partners: start here

New integration partners begin by completing the partner activation form — we review it and grant API access from there. Then continue at step 1 below.

Partner activation form →

ECP clients: authorize your partner

Already an ECP client and want to turn on an integration partner? Submit a partner activation request telling us which vendor to authorize — an account administrator should complete it; allow 3–5 business days.

Partner activation request →
1

Request credentials

Integration partners and direct ECP clients receive a client_id and client_secret from the Eye Cloud Pro team.

2

Get a token

Exchange them at POST /oauth/token — try-able in the reference's Authentication section. Treat your secret like a password.

3

Call the API

Send Authorization: Bearer <token> — or paste the token into the reference and hit Test Request on any endpoint.

4

Go live

Build against staging first — your sandbox client — then switch base URLs to production.

Environments

ProductionLive api.eyecloudpro.com Live practice data — real patients, real invoices. Point production integrations here. StagingSandbox api-staging.eyecloudpro.com Partner sandbox with test data — build and verify your integration here first.

Each environment has its own reference and credentials — switch between them any time with the environment dropdown in the top-right of these pages.

Common questions

FAQ

Tokens, rate limits, time zones, pagination, empty results and errors: how the API behaves across every endpoint. Endpoint-specific rules are on each endpoint's page in the reference.

Read the FAQ →

Stay current

Changelog v2

Every deployment refreshes these docs automatically. The changelog lists new endpoints, parameters, and responses by date.

View the changelog →