Skip to main content

Sevah API

Sevah platform · REST API v1

The Sevah REST API powers Tara, an AI care concierge and companion for aging parents. The API lets authorized customers work with devices, conversations, realtime configuration, and checkout. Integrations use standard HTTPS requests and JSON responses.

Production base URLs
https://app.sevah.ai    - Platform API (devices, conversations, auth)
https://sevah.ai        - Consumer API (Tara checkout, contact, demo)

What you can build​

IdentityAuthenticate securelyExchange a user identity token for a secure session, or issue a scoped token to a registered device.DevicesManage organization devicesList devices, pair rooms, and read or update realtime provider settings.ConversationsRetrieve care conversationsQuery conversation records by organization, facility, or patient context.CheckoutTara subscription checkoutCreate Stripe Checkout sessions for the $249 device lease + $50/month subscription, with coupon support.

Before you start​

You need the following values from your Sevah onboarding or organization administrator:

  • A Sevah user account with access to an organization, or a registered device identity.
  • The authentication material for your integration type.
  • The identifiers for any organization resources your integration will access.

Never place user sessions, device tokens, or identity tokens in client-side logs or shared configuration.

Integration flow​

  1. Authenticate through the appropriate user or device flow.
  2. Send HTTPS requests to the appropriate base URL (see above).
  3. Include JSON request bodies and the required session cookie or bearer token.
  4. Validate every status code and response body before updating local state.

The interactive API reference is the source of truth for available REST operations, request schemas, and response schemas.

Get started​

Make your first requestCreate a session and call a protected endpoint with curl.Tara checkoutStart a Stripe Checkout session for a Tara subscription.Explore the APIBrowse operations, authentication requirements, and schemas.