Dotfile

Dotfile Routines API

The Routines API from Dotfile — 1 operation(s) for routines.

Documentation GitHub OpenAPI

Operations 1

POST /v1/routines/{slug}/trigger Trigger a routine #

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/dotfile-routines-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

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

OpenAPI Specification

openapi: 3.2.0
info:
  title: Dotfile Routines API
  description: Dotfile public API — Routines operations. Split by tag from the OpenAPI Dotfile publishes at https://docs.dotfile.com/openapi/%EF%B8%8F-api-specifications.json (discovered via https://docs.dotfile.com/.well-known/api-catalog). Content is verbatim; only the tag partition is ours.
  version: v1
  contact:
    name: Dotfile Support
    email: support@dotfile.com
    url: https://docs.dotfile.com/reference/getting-help
servers:
- url: https://api.dotfile.com
  description: Production environment
security:
- DotfileAPIKey: []
tags:
- name: Routines
paths:
  /v1/routines/{slug}/trigger:
    post:
      description: "Starts an execution of a routine defined in your Dotfile workspace. The agent runs the routine prompt autonomously; the call returns as soon as the execution is enqueued, and the outcome is reported through the autonomy run webhooks.  \nOnly routines carrying an `external_api` trigger can be fired here — a routine without one or a disabled routine is refused with a `409`. Scope the execution to a case with `case_id`, or leave it out to run across the whole workspace.\n\n"
      operationId: routine-trigger-routine
      parameters:
      - name: slug
        required: true
        in: path
        description: Identifier of the routine, generated from its title at creation and stable across renames. Shown in the console on the routine settings.
        schema:
          type: string
      requestBody:
        required: false
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/TriggerRoutine'
      responses:
        '201':
          description: 'The execution started


            **ℹ️ Click to see full payload**'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/RoutineTriggered'
        '400':
          description: "The request is either malformed or contain invalid parameters.\n\n  - Make sure the body payload matches the expected schema\n  "
        '404':
          description: No routine can be found.
        '409':
          description: The routine cannot be triggered because it is disabled or carries no external API trigger.
      summary: Trigger a routine
      tags:
      - Routines
components:
  securitySchemes:
    DotfileAPIKey:
      type: apiKey
      in: header
      name: X-DOTFILE-API-KEY
      description: Configure your api key in the Workspace settings