A real API

A real API, described by the code that validates it

Create meetings, add people, read attendance and sign somebody in — versioned, and documented by a specification that cannot drift from the implementation.

What you can do with it

Create a meeting and get a join link back. Add people to it in bulk. Read who attended and for how long. Mint a short-lived sign-in for one of your users. Enough to make SeeUAll the meeting layer under something you already have, rather than a second place your people go.

Authenticated per organisation with a key you issue and can revoke.

The specification is generated, not written

The machine-readable description of the API comes from the same definitions the routes validate incoming requests against. It cannot describe a field the code does not accept, and a route that adds one it cannot see fails the build.

Hand-written API documentation is accurate on the day it is written. This is accurate because it has no separate existence.

Read next

  • Webhooks

    Meeting started, meeting ended, attendance settled, recording ready — signed, retried, and dead-lettered rather than dropped.

  • Single sign-on

    From the system your organisation already runs, with nobody keeping another password.

  • It plugs into the system you already run

    From your timetable, your learning platform, or your own software — with the right people already invited, and what happened sent back.

Everything it does

Want to see this working?

Tell us what you are trying to do with it and we will show you that, rather than a tour of everything else.

info@seeuall.com
    A real API — SeeUAll · SeeUAll