deep thought cloud
SvenskaStart free

Your own system, through the API

Send recordings in from your own system, or take transcripts, summaries and actions out, over the REST API.

Plan: Enterprise

For a developer who wants recordings in, or knowledge out, from their own system: a CRM, a case system, an internal tool.

The REST API is the platform the apps themselves use: upload, processing status, sources with transcript and extraction, search and actions.

Sketch: a blank card passing through a mail slot and continuing as smaller cards sorted into three trays; the slot rim carries the gradient.

What you need

  • Enterprise: ask us about API access.
  • A token for your account: today a device token that we issue, starting with dtd_, sent as Authorization: Bearer.
  • A system that can make HTTPS requests.

Steps

  1. Your system
  2. The REST API
  3. Sources and extraction
  4. Back in your system

  1. Step 1: Ask for API access

    Write to us. We issue the account’s token; it is shown once, so store it as a secret.

  2. Step 2: Read the reference

    The API reference has every endpoint and a quick start.

  3. Step 3: Upload a recording

    POST /sources/upload with the file answers with a task id; GET /sources/tasks/{task_id} gives the source once it exists.

  4. Step 4: Read the result

    Poll GET /sources/{id}/status until it is done, then read GET /sources/{id} for the transcript and extraction. POST /search and GET /actions work across all your sources.

What happens next

  • The same sources and extraction the apps use, in your own system.
  • What you send over the API is in the Web App too.
  • The token can be revoked at any time in the Web App, under Inställningar.

Read more

Stuck? E-mail support@deep-thought.cloud.

All use cases