Developers

DDS Matchmaker API

The REST API behind DDS Matchmaker. Blog posts and the expert directory are open to read without credentials; everything else needs a bearer token. All responses are JSON, with the payload under data.

Reference

• OpenAPI 3.0 spec

  Every operation, parameter and response schema.

• Interactive docs

  Try requests in the browser.

• API catalog (RFC 9727)

  Machine-readable pointer to the spec and docs.

• Agent index

  This page as plain text for agents.

Base URL

https://api.ddsmatchmaker.net

Quickstart: no credentials

curl "https://api.ddsmatchmaker.net/blogs?page=1&limit=10"
curl "https://api.ddsmatchmaker.net/blogs/<slug>"
curl "https://api.ddsmatchmaker.net/experts?page=1&limit=10&search=implant"
curl "https://api.ddsmatchmaker.net/experts/<id>"

GET /experts also filters by location, skills, tags, availability, engagement type and sort order; the spec lists the values.

Authentication

Create an account at app.ddsmatchmaker.net, then exchange its credentials for a token:

curl -X POST "https://api.ddsmatchmaker.net/auth/login" \
  -H "Content-Type: application/json" \
  -d '{"email":"you@example.com","password":"..."}'

The token is at data.token. Send it on every request as Authorization: Bearer <token>. An unverified email gets 403 and a fresh one-time code by email.

Errors

Errors are JSON with the matching HTTP status, for example 404 {"message":"Blog not found"}, or 401 on a missing or expired token.

Rate limits

Every response carries RateLimit and RateLimit-Policy headers, currently 60 requests per 60 seconds, so clients can throttle before hitting a 429.

Support

support@networkdental.us