Build with Aimedis.
Start with the right API.
Connect your AI to reviewed Wiki evidence, or plan an integration with Aimedis care platforms. Each service has its own access requirements and data contract.
Aimedis Wiki · AI integration
Your model. Traceable evidence.
Retrieve approved reference excerpts from Wiki over HTTP, then pass them to your chosen AI. Preserve the source, version and licence with every answer.
POSThttps://wiki.aimedis.com/api/reference/v1/retrieveAuthorization: Bearer awr_…
Arrange access
Ask a Wiki administrator to issue an API key (awr_…) for your application in Integrations, and store it only on your server.
Retrieve evidence
Send a general knowledge query from your application server.
Ground your answer
Give excerpts to your AI and show citations or insufficient evidence.
Authenticate with Authorization: Bearer <awr_ key>. A Wiki administrator issues each key once in Integrations, bound to one application; administrator sessions and browser cookies are not accepted by this API. Keys can be issued for any Aimedis application or a custom application ID; each key reads every published, reviewed reference source of its organization, within 30 requests per minute.
Understand the platform before you connect.
These guides explain partner onboarding, patient consent and the platform architecture. Confirm the service URL, credentials, record-read contract and availability with Aimedis before implementing the illustrative examples.
Reference documents follow your selected language.
Integration overview
Developer Guide
Patient-consent concepts, care workflows and specialist module integration patterns.
Read documentAccess & onboarding
Partner Onboarding
Access requests, credential requirements and a checklist to agree before going live.
Read documentContract overview
Platform API Overview
Illustrative clinical endpoint shapes and the contract details to confirm with the owning service.
Read documentArchitecture
System Architecture
How care applications, consent and the separate Wiki reference library fit together.
Read documentPlanning a platform integration?
Tell us which product, workflow and data you need. Agree the service contract and access scope before sending requests.