WisePaws Partner API
Consult audio in, structured clinical note out.
This API is for practice management systems that want WisePaws note generation inside their own product. A vet connects their WisePaws account to you once. After that, the whole integration is three calls per consult:
- Submit the recording from your backend, under an idempotency key you generate.
- Poll until it is ready. Transcription and generation run without you, and the note comes back as sections with stable keys you map your own fields onto.
- Report what the vet did with it. Optional, and the only measure either of us gets of whether the note was worth keeping.
Setting up a practice, joining one, and subscribing all happen on WisePaws. None of it needs anything from you, and there is no API for any of it.
Start here
New to the API: the quickstart gets you from nothing to a note in four curl calls.
Building it properly: how an integration fits together covers the two things that are easy to get wrong and expensive to discover later, which are how tokens are scoped and how notes are addressed.
Designing the unhappy path: when a consult fails. A consult cannot be re-recorded, so this is the guide that decides whether a bad day costs the vet a record or two minutes.
Looking up a field, an enum or an error code: the reference is generated from the API specification. It also carries the current release status and the compatibility rules. Where anything on these guide pages disagrees with it, the reference is right and we have a bug to fix.
What you need from us
A client_id, a client_secret, and at least one registered redirect URI. Ask and we will issue them, along with a separate sandbox pair so you can build and test the whole integration before a real consult goes anywhere near it.