Skip to content
dhanu docs
Browse pages
Changelog Join our community Contact support

Authentication

Overview

Sandbox workspace

One click in the developer console creates a throwaway workspace with sample staff, a project, tasks, a workflow and a file, plus a test key, so you can try every read endpoint against real rows.

A test key answers generation calls with fixtures, but the endpoints that read, tasks, staff, workflows, files, projects, return whatever the workspace holds. A brand-new workspace holds nothing, which makes the first hour with the API oddly empty. The sandbox fixes that.

Create one

In the developer console, Get started → Create a sandbox workspace. Dhanu makes a new personal workspace called API Sandbox owned by you and seeds it with:

  • two staff members hired from the template catalogue
  • a project with two tasks
  • a workflow with one {{topic}} field
  • a README file in your drive
  • a developer project named Sandbox with a test-mode key, shown once

Your browser switches to the sandbox and the key is on screen. Nothing in it costs credits to read, and generation calls with the test key spend nothing either.

export DHANU_API_KEY=dhanu_sk_test_…
curl https://api.dhanu.ai/api/pub/v1/staff -H "Authorization: Bearer $DHANU_API_KEY"
curl https://api.dhanu.ai/api/pub/v1/workflows -H "Authorization: Bearer $DHANU_API_KEY"
curl https://api.dhanu.ai/api/pub/v1/tasks -H "Authorization: Bearer $DHANU_API_KEY"

When you are done

It is an ordinary workspace: it counts towards your workspace limit, and you delete it from Settings → Workspaces like any other. Make as many as the limit allows; each one is seeded the same way.