Developer tools

DigitalStack Postman collection

Import a ready-made workspace for exploring the DigitalStack REST and GraphQL APIs. Authentication, variables, request tracing, examples, and response checks are already configured.

A small, useful starting point

The collection now grows alongside capability promotion. Each capability folder includes runnable REST requests and GraphQL coverage where the runtime exists; planned GraphQL requests are labeled as planned so customers can review the target contract without confusing it for a shipped interface.

Choose how to download

Use the blank collection with any key you already hold, or create a dedicated Postman key and receive a ready-authenticated collection.

Blank collection

Import the collection, then set api_keyonce in collection variables. Every REST and GraphQL request inherits it automatically, while resource visibility still follows that key's creating user.

Download blank collection

Personalized collection

Create a new dedicated key with every explicit public API scope, inject its one-time value locally, and download a collection that is ready to send. The key can use every capability, but it only sees resources the creating user can see.

The blank collection remains available without signing in.

Existing keys cannot be selected for injection because DigitalStack stores only their hash and display prefix. Their raw values are intentionally unretrievable after creation.

What is a Postman collection?

A collection is a portable JSON file containing API requests and their shared setup. After importing it into Postman, you can configure authentication once, inspect or change each request, send it, and view the response without writing a client first. Choose a blank download with no credentials, or generate a dedicated Postman key during download.

REST examples

GET /api/v1/me/today · POST /api/v1/work-item-enhancements

Capability folders include ready-to-run REST requests with scoped authentication, parameters, request IDs, and response-shape checks.

GraphQL examples

POST /api/graphql

Shipped operations are runnable. Planned operations are intentionally named with[Planned] and document the target shape before implementation.

Import it and make a request

Choose a blank or personalized download

The blank download lets you reuse a key you already hold. The personalized option creates a dedicated, expiring Postman key and injects it into the file locally. Then open Postman, choose Import, and drop in DigitalStack.postman_collection.json.

Use scopes that match the APIs you want to run

The collection is designed to grow across the complete public API. Each request names its required scope. The personalized flow grants its dedicated key every explicit public API scope currently available; for a blank download, grant your key the scopes required by the requests you intend to use.

Scopes grant permission to use an API capability. They do not grant visibility to every resource in the account, so list and detail responses still reflect the key creator's account, user, project, workspace, team, and engagement visibility.

Create or manage API keys

Set authentication once for every API

REST and GraphQL requests inherit one collection-level Bearer credential. Personalized downloads arrive with api_keypopulated. For blank downloads, open the collection's Variables tab and enter it once.

Collection variables

base_urlstringrequired

DigitalStack host without a trailing slash. The collection defaults to local development; use https://www.digitalstack360.com only for endpoints deployed to production.

Example: http://localhost:3001

api_keysecretrequired

The single shared dsk_…API key inherited by every request. Keep it out of source control and shared collection exports. The key's scopes unlock capabilities; the key creator's resource visibility still bounds results.

workspace_idUUIDoptional

Required by GraphQL requests that ask for an explicit workspace. Most REST requests derive workspace access from the API key.

page_sizeintegerrequired

Default page size for list-style requests, from 1 to 100.

Example: 20

work_item_id / time_entry_id / enhancement_run_idstringoptional

Capability-specific placeholders used by detail and command examples. Replace them with real records from your workspace before sending those requests.

Send a request

Open a capability folder such as Documents or Today & My Workand choose a REST or GraphQL request. Select Send. Postman will display the response and run the included checks for status, JSON content, and response shape.

Personalized downloads contain a live credential

Blank downloads contain no key. Personalized downloads contain the newly generated key in the shared api_key variable. Do not commit or share that file, and revoke its key immediately if it is exposed or no longer needed.

What the collection handles for you

Shared authentication

Set one Bearer API key at collection level; every REST and GraphQL request inherits it.

Useful defaults

Production URL, pagination, optional filters, and GraphQL variables are ready to edit.

Fast feedback

Request IDs aid tracing, while included tests catch transport and response-shape errors.

Ready to try it?

Download a fresh copy whenever new endpoints are added to the collection.

Choose download