OAuth 2.0 (Client Credentials or Authorization Code flow)
500 requests per minute per API key 2. Authentication 2.1 Get Access Token POST /oauth/token Host: auth.bronson.io Content-Type: application/x-www-form-urlencoded client_id=YOUR_CLIENT_ID &client_secret=YOUR_CLIENT_SECRET &grant_type=client_credentials &scope=patient.read appointment.write api bronson
"url": "https://your-app.com/webhook/bronson", "events": ["appointment.created", "lab.result.available"], "secret": "your-verification-token" OAuth 2
"appointment_id": "APT-9876", "status": "confirmed", "location": "Main Clinic - Suite 200" Overview API Bronson provides programmatic access to patient
All errors return standard HTTP status codes with a JSON body:
"error": "invalid_request", "message": "Missing required field: patient_id", "status": 400
If you have a specific Bronson API (e.g., Bronson Healthcare, Bronson Labs), this guide gives you a template to adapt. Version 1.0 | REST | JSON | OAuth 2.0 1. Overview API Bronson provides programmatic access to patient records, scheduling, clinical data, and billing information. It follows REST principles and uses standard HTTP methods.