Content APIs
Documents, folders, files and images, pulled in bulk. The whole sheet, as the clinic wrote it.
Search APIs
Term search across everything, with filters, date ranges, Lucene queries and regex.
Artefact APIs
The Digital Orchestrator: curated artefacts, built for voice. An editor saves, and Peach knows.
Live APIs
Knowledge pushed into a named agent’s Panviva client, so humans see what Peach sees.
4.
steps
from a developer key to live knowledge, once, through Panviva’s own APIs.
Panviva Content Admin
The clinic’s own knowledge owner, holding the instance and deciding what is in scope.
1 2
Avaamo Integration Engineer
Connects to the APIs, ingests the sheet, and validates every endpoint before go-live.
3 4
Step 01
Developer access Register on dev.panviva.com and take the API key for the clinic’s instance at api.panviva.com.
Step 02
Scope the content Point at the Center for Pediatric Wellness folders: the static sheet, and the curated artefacts.
Step 03
Connect & ingest Avaamo authenticates, pulls the whole sheet over the Content and Search APIs, and indexes it.
Step 04
Verify & go live Every endpoint answered and spot-checked; artefact updates then flow in real time, on their own.
1
The clinic’s knowledge
Center for Pediatric Wellness, as the clinic wrote it.
Static content Documents, folders, images.
Dynamic content Artefacts, built for voice.
2
Content & Search APIsBulk · both ways
3
Digital Orchestrator APIReal time · both ways
4
Avaamo
Ingestion, guardrails, orchestration. Artefact changes applied the moment they land.
5
Grounded answersClinic line · both ways
6
Peach
Every answer traced back to the sheet it came from.
All third-party names and logos — Children’s Healthcare of Atlanta, Epic, Panviva, Webex by Cisco, MyChart — are trademarks of their respective owners, shown for identification only. Avaamo is not affiliated with or endorsed by them.
On the clinic line