CoachAccountable Plays Well With AI Agents Thanks to the API
CoachAccountable has had a rich API for most of its life (the API was originally released in 2015, over 11 years ago!). For most of that time, using that API was largely limited to larger firms, which makes sense. Those have traditionally been the ones with operational scale to really benefit from the sort of automations possible by an API, coupled with the resources to actually get something built.
But here in the advent of AI with myriad agents capable of transacting on behalf of users via publicly exposed APIs, the presence of CA’s API is now meaningfully useful for a much broader audience. And it shows! There’s been a tidy but quite noticeable surge of requests for additions and enhancements to that API, to suit workflows that are suddenly coming into view as useful.
For example, last week we got this request:
Here’s another thing that would be really nice: the ability to send `isDraft` when I call Session.add so that I can leave session notes in a drafted state, not have them automatically completed.
Here’s my use case: when I complete client sessions, my assistant processes the transcript to get my follow up notes and action items using a private GPT, which gets me to about 75% of the way to a solid follow-up. Then later in the day, I log in to review action items and session notes.
So it would be incredibly helpful to have the draft that I’m still responsible for reviewing and approving, and so helpful if action items would be ready and waiting for me as the coach as well.
This sort of thoughtful request warms my heart, especially because I’m leery of AI crowding out the personalized magic that I, speaking as a coaching client (and by extension, speaking on behalf of some non-zero swathe of coaching clients in general) enjoy receiving from a thoughtful, caring coach. It speaks to using AI as a leg up towards, rather than a substitute for, the delivery of thoughtful work product to clients. So I am all too happy to ensure the CoachAccountable API supports such use cases.
As another example, I’ve heard interest in piping session notes in from numerous note-taking AIs. Because those products are in flux with new ones coming out regularly, it doesn’t make sense for me to build full-on integrations with each one. But because AI knows how to AI, session notes from whichever source can readily post whatever into CA via the Session.add API function, or one of the ClientFile add functions.
The CA API makes it especially easy to post things to a given client’s file using it’s support for email addresses as user ID aliases: rather than needing a separate step to figure out the internal ID for a given client as a separate step, for example, an external AI agent can use what it probably already knows about your client in an external context (namely their email address), and use that to post some notes or a file for them.
It remains the case as much today as it did back in 2015 that I’m happy to add API functionality to suit use cases that aren’t already supported. Some things aren’t as practical to do via API as they are in-app (I’m looking at you, Course Builder!), but other, more transactional bits are certainly worth bringing towards feature parity with the app itself as they prove useful. Now that the coding part to interact with it can be trivially cooked up by AI, we may as well ensure CA API is up to the job of supporting the automations that users seek!





















