API v1 · PREVIEWSAMPLETHE NOTES →

Build for the practices of the next generation.

One REST API, OpenID Connect sign-in and signed webhooks. Ship your dental software where owners and young doctors already shop for tools, and pass a security and HIPAA review run by people who know dentistry.

Start a submission npm i -g @ddshub/cliSAMPLE
SAMPLE
# install the DDS Hub CLI$ npm i -g @ddshub/cli# sign in with your developer account$ ddshub login✓ Authenticated as alex@acmedental.com # scaffold a listing, then submit it for review$ ddshub apps create smilesync --group patients$ ddshub submit smilesync --phi✓ Submitted · review #2481 queued← You'll get an email at every stage
SAMPLE · API PREVIEW SHELL
AUTH
OAuth 2.0 · OpenID Connect
TRANSPORT
REST · JSON · TLS 1.2+
EVENTS
HMAC-signed webhooks
REVIEW
Human · by people who know dentistry
01 / PLATFORM

Four primitives. A storefront that speaks dentist.

Practices come here ready to choose. Plug into the same sign-in, bill and feedback loop as every app in the suite.

API PREVIEW · SAMPLE ENDPOINTS
AUTH

Single sign-on

Practices open your app already signed in. Standard OpenID Connect, so the front desk never makes another password.

  • GET /.well-known/openid-configuration
  • POST /oauth/token
BILLING

One bill

Charge on the practice’s single DDS Hub invoice. Report seats or usage; we collect and pay out.

  • POST /v1/billing/usage
  • GET /v1/billing/payouts
EVENTS

Install events

Know the moment a practice adds or removes your app. Every delivery is signed and retried.

  • EVENT app.installed
  • EVENT app.uninstalled
FEEDBACK

Practice feedback

Read the notes practices send your team from their workspace, and reply in one place.

  • GET /v1/apps/{id}/feedback
  • EVENT feedback.created
02 / REVIEW PIPELINE

Four stages, reviewed by real people.

We check security, patient-data handling and whether your app solves a real problem for a dental practice. Every stage reports back by email.

VIEW PREFLIGHT CHECKS →
review #2481 acme-dental/smilesync · sample run SAMPLE · 3 OF 4
  1. Create a developer account PASSED · 00:42 account.verify Company details and a verified work email. We confirm every company before review.
  2. Submit your app PASSED · 03:10 app.submit Name, category and the problem it solves. Add icon, screenshots and pricing any time.
  3. Security and HIPAA review RUNNING security.hipaa We sign in with a test login you provide, check data handling and confirm a BAA if you touch PHI.
  4. Go live QUEUED listing.publish Your listing is published and practices can add your app in one tap.
$ ddshub review status smilesync✓ tls          TLS 1.2+ on every endpoint✓ encryption   at rest and in transit✓ access       roles, MFA and audit log● baa          awaiting signature○ listing      queued for copy review
03 / PREFLIGHT

What we check before you go live.

  • use_case A real dental use case The app solves a problem practices actually have, stated in one sentence. REQUIRED
  • data_handling HIPAA-ready data handling Encryption in transit and at rest, access controls and audit logs. REQUIRED
  • baa A signed BAA Required for any app that stores or processes patient data. IF PHI
  • test_login A reviewer test login Sample, non-patient data so our team can use the app end to end. REQUIRED
  • pricing Clear pricing What a practice pays and what is included, with no hidden fees. REQUIRED
  • support Responsive support A named contact and a support channel practices can reach. REQUIRED
04 / SPEC · DRAFT · SAMPLE

Boring infrastructure, on purpose.

BASE URL
https://api.ddshub.app/v1
SANDBOX
https://sandbox.api.ddshub.app/v1
AUTH
API keys (Bearer) for your server · OAuth 2.0 + OIDC for practice sign-in
VERSIONS
Dated, pinned per key · 2026-11-01
WEBHOOKS
HMAC-SHA256 signature · retried with backoff
LIMITS
Per key, per minute · shared with approved developers
PHI
Encrypted in transit and at rest · BAA required before any PHI
EVENT · APP.INSTALLED SAMPLE
POST /hooks/ddshub HTTP/1.1X-DDS-Event: app.installedX-DDS-Signature: t=1794039825,v1=5f2b…c9e1 {  "id": "evt_01JC8W3Q",  "type": "app.installed",  "created": 1794039825,  "data": {    "practice": { "id": "prc_7Hq2", "name": "Bayfront Dental" },    "seats": 6,    "plan": "pro",    "baa_signed": true  }}
05 / SUBMIT AN APP

Start with the basics. We’ll take it from there.

It takes about five minutes. You can add your icon, screenshots and pricing after you submit.

  1. 1 Tell us who you areCompany details and a work email we can reach.
  2. 2 Submit your appName, job and the problem it solves.
  3. 3 Security and HIPAA reviewOur review team checks data handling, BAA and fit.
  4. 4 Go liveYour app is listed and practices can add it.
REQUEST PREVIEW SAMPLE API
POST /v1/developers HTTP/1.1Authorization: Bearer •••• {  "company": "",  "contact": "",  "email": "",  "website": "",  "terms_accepted": false}
○ waiting for required fields
ddshub › new-submission
$ STEP 1/2 · WHO YOU ARE

Tell us who you are

Use your work email. We verify every company before review.

Your app
Job it does
Icon and up to 5 screenshots can be added after you submit.
06 / QUESTIONS

Before you submit.

It depends on the app and on whether it handles patient data. We email you at each step and tell you exactly what to change if anything is missing.