Authentication
All Nevatal API endpoints require authentication via API keys. Your API key identifies your clinic and determines the scope of data you can access.Getting your API key
- Log into your Nevatal dashboard at app.nevatal.com
- Navigate to Settings → API Keys
- Click Create API Key
- Select the scopes (permissions) your integration needs
- Copy and securely store the generated key
Using your API key
Include the API key as a Bearer token in theAuthorization header of every request:
Scopes
API keys are scoped to specific modules. When creating a key, you select which modules it can access:| Scope | Read | Write | Description |
|---|---|---|---|
patients | ✅ | ✅ | Patient records and demographics |
appointments | ✅ | ✅ | Appointment scheduling and management |
billing | ✅ | ✅ | Invoices, payments, and credit notes |
emr | ✅ | ✅ | Medical records, prescriptions, clinical notes |
clinical-procedures | ✅ | ✅ | Procedure catalog and management |
locations | ✅ | ❌ | Clinic location information |
Key management
Revoking a key
Listing active keys
Security best practices
Never expose keys in client-side code
Never expose keys in client-side code
API keys should only be used in server-to-server communication. Never include them in frontend JavaScript, mobile apps, or public repositories.
Use the minimum required scopes
Use the minimum required scopes
Only grant the scopes your integration actually needs. A billing integration doesn’t need EMR access.
Rotate keys regularly
Rotate keys regularly
Create new keys periodically and revoke old ones. This limits the impact of a compromised key.
Use environment variables
Use environment variables
Store API keys in environment variables or a secrets manager, never hardcoded in source files.

