DoiT

DoiT Folders API

Organize Cloud Analytics resources (reports, allocations) into folders.

GitHub OpenAPI

Operations 5

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /analytics/v1/folders List Cloud Analytics folders · List folders #
Ask an LLM
“What folders do we have for organizing reports?”
“Can I page through all Cloud Analytics folders?”
Tell an agent
List all folders.
Show me Cloud Analytics folders, {n} per page.
POST /analytics/v1/folders Create a folder · Create a folder #
Ask an LLM
“How do I make a folder to organize reports and allocations?”
“Can I create a subfolder inside another folder?”
Tell an agent
Create folder {name}.
Create folder {name} inside folder {parentFolderId}.
GET /analytics/v1/folders/{id} Retrieve a folder · Get a folder #
Ask an LLM
“How do I see one folder's details?”
“Can I look up a folder by ID?”
Tell an agent
Get folder {id}.
Show me folder {id}.
PATCH /analytics/v1/folders/{id} Rename or move a folder · Update a folder #
Ask an LLM
“How do I rename an existing folder?”
“Can I move a folder under a different parent or back to the top level?”
Tell an agent
Rename folder {id} to {name}.
Move folder {id} under {parentFolderId}.
DELETE /analytics/v1/folders/{id} Delete a folder · Delete a folder #
Ask an LLM
“What happens to reports when I delete their folder?”
“Does deleting a folder also remove its nested folders?”
Tell an agent destructive · confirm first
Delete folder {id}.
Remove folder {id} and its subfolders.

Documentation

📖
Documentation
https://developer.doit.com/docs/start
📖
APIReference
https://developer.doit.com/reference/welcome
📖
GettingStarted
https://developer.doit.com/docs/start
📖
Authentication
https://artifacts.apis.io/doit/authentication/doit-authentication.yml
📖
RateLimits
https://artifacts.apis.io/doit/rate-limits/doit-rate-limits.yml

Specifications

⚙
OpenAPI
https://artifacts.apis.io/doit/openapi/doit-folders-api-openapi.yml

Other Resources

🔗
OAuthScopes
https://artifacts.apis.io/doit/scopes/doit-scopes.yml
🔗
ErrorCatalog
https://artifacts.apis.io/doit/errors/doit-problem-types.yml
🔗
DataModel
https://artifacts.apis.io/doit/data-model/doit-data-model.yml
🔗
Conventions
https://artifacts.apis.io/doit/conventions/doit-conventions.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/doit:doit-folders-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

doit-folders-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: DoiT Folders API
  description: Programmatic access to DoiT Platform
  version: v1
servers:
- url: https://api.doit.com
security:
- api_key: []
- tenantId: []
  api_key: []
tags:
- name: Folders
  description: Organize Cloud Analytics resources (reports, allocations) into folders.
paths:
  /analytics/v1/folders:
    get:
      tags:
      - Folders
      summary: List folders
      description: 'Returns Cloud Analytics folders the current customer has access to.

        Folders are returned in id-ascending order.'
      operationId: listFolders
      parameters:
      - $ref: '#/components/parameters/maxResults'
      - $ref: '#/components/parameters/pageToken'
      responses:
        '200':
          description: OK - The request succeeded.
          content:
            application/json:
              schema:
                type: object
                properties:
                  pageToken:
                    type: string
                    description: Page token, returned by a previous call, to request the next page of results.
                  rowCount:
                    type: integer
                    description: Number of folders returned in this page.
                  folders:
                    type: array
                    items:
                      $ref: '#/components/schemas/Folder'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '500':
          $ref: '#/components/responses/500'
    post:
      tags:
      - Folders
      summary: Create a folder
      description: Creates a new Cloud Analytics folder.
      operationId: createFolder
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/CreateFolderRequest'
      responses:
        '201':
          description: Created - The folder was created.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Folder'
          links:
            getFolder:
              operationId: getFolder
              parameters:
                id: $response.body#/id
            updateFolder:
              operationId: updateFolder
              parameters:
                id: $response.body#/id
            deleteFolder:
              operationId: deleteFolder
              parameters:
                id: $response.body#/id
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '500':
          $ref: '#/components/responses/500'
      x-codegen-request-body-name: Body
  /analytics/v1/folders/{id}:
    get:
      tags:
      - Folders
      summary: Get a folder
      description: Returns the specified Cloud Analytics folder.
      operationId: getFolder
      parameters:
      - name: id
        in: path
        description: Folder ID.
        required: true
        schema:
          type: string
      responses:
        '200':
          description: OK - Folder returned.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Folder'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '500':
          $ref: '#/components/responses/500'
    patch:
      tags:
      - Folders
      summary: Update a folder
      description: 'Updates the specified folder. All fields are optional.

        To reparent the folder, set `parentFolderId` to the target folder ID

        (use "root" for the top level). If a sibling at the target has the same

        name, the folder is auto-renamed.

        To move reports or allocations into or out of a folder, update the item''s

        `folderId` field via the report or allocation PATCH endpoint.'
      operationId: updateFolder
      parameters:
      - name: id
        in: path
        description: Folder ID.
        required: true
        schema:
          type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/UpdateFolderRequest'
      responses:
        '200':
          description: OK - Folder updated.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Folder'
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '500':
          $ref: '#/components/responses/500'
      x-codegen-request-body-name: Body
    delete:
      tags:
      - Folders
      summary: Delete a folder
      description: Deletes the specified folder. All nested folders will be deleted. Any reports or allocations contained in the folder are moved to the root.
      operationId: deleteFolder
      parameters:
      - name: id
        in: path
        description: Folder ID.
        required: true
        schema:
          type: string
      responses:
        '204':
          description: No Content - Folder deleted.
        '400':
          $ref: '#/components/responses/400'
        '401':
          $ref: '#/components/responses/401'
        '403':
          $ref: '#/components/responses/403'
        '404':
          $ref: '#/components/responses/404'
        '500':
          $ref: '#/components/responses/500'
components:
  schemas:
    Folder:
      type: object
      description: A Cloud Analytics folder.
      properties:
        id:
          type: string
          description: Folder ID.
        name:
          type: string
          description: Folder name.
        description:
          type: string
          description: Folder description.
        parentFolderId:
          type: string
          description: Identifier of the parent folder. Set to "root" if the folder is at the top level.
          default: root
          example: root
    Error:
      type: object
      description: Standard error response structure.
      properties:
        error:
          type: string
          description: Detailed error message.
    UpdateFolderRequest:
      type: object
      description: 'Request body for updating a folder. All fields are optional; only fields

        the caller wants to change should be set.'
      properties:
        name:
          type: string
          description: Folder name.
        description:
          type: string
          description: Folder description.
        parentFolderId:
          type: string
          description: Identifier of the new parent folder. Use "root" to move the folder to the top level. If a sibling at the new parent has the same name, the folder is auto-renamed (e.g. "Foo" → "Foo (1)").
          default: root
          example: root
    CreateFolderRequest:
      required:
      - name
      type: object
      description: Request body for creating a folder.
      properties:
        name:
          type: string
          description: Folder name.
        description:
          type: string
          description: Folder description.
        parentFolderId:
          type: string
          description: Identifier of the parent folder. Use "root" or omit to place the folder at the top level.
          default: root
          example: root
  parameters:
    maxResults:
      name: maxResults
      in: query
      description: The maximum number of results to return in a single page. Use the page tokens to iterate through the entire collection.
      schema:
        type: integer
        format: int64
        default: 50
    pageToken:
      name: pageToken
      in: query
      description: Page token, returned by a previous call, to request the next page of results
      schema:
        type: string
  responses:
    '404':
      description: Not Found - The requested resource does not exist.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    '401':
      description: Unauthorized - Invalid API key.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    '403':
      description: Forbidden - The client is not authorized to perform the request.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    '500':
      description: Internal Server Error - Something went wrong with the DoiT API server.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
    '400':
      description: Bad Request - The server cannot process the request, often due to a malformed request.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
  securitySchemes:
    api_key:
      type: apiKey
      name: Authorization
      description: Use the "Bearer <API_KEY>" format or sign in for autofill
      in: header
    tenantId:
      type: apiKey
      name: X-Tenant-Id
      description: 'Customer (tenant) ID for the request. Separate from your API token: always authenticate with `Authorization: Bearer <token>` (personal or service account). See [Get Started](https://developer.doit.com/docs/start). Omit when your token is scoped to a single customer (resolved automatically). A service account can select an active direct or nested descendant of its home customer; the endpoint''s normal permissions, entitlements, and resource-ownership checks still apply. A service-account target outside that customer subtree returns `403 Forbidden`. Prefer this header over the legacy `customerContext` query parameter, which only applies to legacy API keys and is ignored by personal and service account tokens.'
      in: header
    oauth2:
      type: oauth2
      flows:
        authorizationCode:
          authorizationUrl: https://console.doit.com/sign-in/oauth
          tokenUrl: https://console.doit.com/api/auth/token
          scopes:
            dci: Access All Data
x-samples-languages:
- curl
- go
- node
- python
x-cli-config:
  security: oauth2
  params:
    client_id: cli
x-provenance:
  method: harvested
  publisher: DoiT
  source: https://api.doit.com/openapi.yaml
  note: split by refine-openapis from the provider's own published document, verified by fetch (openapi/_original/*.fetch.json);
    stamped by stamp-openapi-provenance.py (roadmap#793)