¶ API Integration
Salvus Health provides a secure and modern RESTful API to enable seamless integration with third-party systems. The API supports robust interactions between our patient engagement platform and your pharmacy information system, ensuring data consistency and real-time synchronization where needed.
¶ Authentication
All API requests require secure authentication. Clients must first request an access token from Salvus Health’s authorization server. This token grants time-limited access to make HTTPS requests to Salvus Health services, using OAuth 2.0 industry-standard authentication protocols.
¶ Patient profiles and data synchronization
The API integration should allow for the creation and synchronization of patient profiles between Salvus Health and third-party applications. This will ensure a unified view of the patient across both platforms and supports smooth workflows, such as bookings, care flows, and follow-ups.
¶ Versioning and stability
The Salvus Health API is versioned to ensure backward compatibility and stable integrations over time. Partners will be notified of any breaking changes well in advance.
¶ Support and developer resources
Our development team provides support during the integration process, including sandbox access and technical guidance when needed.
¶ Data privacy and compliance
All data exchanges between Salvus Health and third-party applications's platform will comply with GDPR data protection requirements. A separate Data Sharing or Processing Agreement will govern roles, responsibilities, and security protocols.
No patient data will be shared without lawful basis and appropriate patient consent where required and the sharing of patient data shall be limited to what is necessary for the purposes of the integration between the patient engagement system and the pharmacy information system. Each party will be responsible for implementing and maintaining appropriate security measures to protect patient information.
¶ Getting Started
You need access token to be able to make authorized requests. We use OAuth 2.0 standard protocol.
Each access token is bound to a specific organization (pharmacy).
¶ Authorization Process
You can request the access token from Salvus-Health after reaching an agreement. The token will be shared via a secure channel and will have a long expiration period based on specific agreement.
If you believe the token has been compromised, Salvus can revoke it at any time upon request.
¶ 
Using Access Token
Once you've received your access token make sure you add the string "Bearer" to your authentication headers as shown below.
--header 'Authorization: Bearer 2FB3CEC7B1D62D8045169544A9DC2313613B525F06F2C96E29302FB-1'
Each access token is tied to a specific organization (pharmacy), so you must use the correct token for each one.
¶ Base URL
The base url depends on the envronment you want to use. For testing use sandbox environment, for real api calls use the production base url
¶ SANDBOX
https://api.sandbox.salvus-health.com
¶ PRODUCTION
https://api.salvus-health.com