Treasure Data

Treasure Data Agent Schedule API

The AgentSchedule API from Treasure Data — 4 operation(s) for agentschedule.

GitHub OpenAPI

Operations 7

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 /api/agent_schedules List agent schedules · index #
Ask an LLM
“Which agents are set to run on a schedule?”
“Can I list schedules for just one agent or one project?”
Tell an agent
List all agent schedules.
List schedules for agent {agentId}.
POST /api/agent_schedules Schedule an agent · create #
Ask an LLM
“Can I make an agent run automatically on a schedule?”
“What does a new agent schedule need?”
Tell an agent
Create an agent schedule with {data}.
Schedule an agent run using payload {data}.
DELETE /api/agent_schedules/{id} Delete an agent schedule · destroy #
Ask an LLM
“Can I stop an agent from running on its schedule for good?”
“What removes a scheduled agent run?”
Tell an agent destructive · confirm first
Delete agent schedule {id}.
Remove the schedule {id} so the agent stops running automatically.
GET /api/agent_schedules/{id} Get an agent schedule · show #
Ask an LLM
“When does a particular agent schedule run next, and what does it run?”
“Can I fetch one agent schedule with its related records?”
Tell an agent
Show agent schedule {id}.
Get agent schedule {id} including {include}.
PATCH /api/agent_schedules/{id} Update an agent schedule · update #
Ask an LLM
“Can I change when a scheduled agent runs?”
“Which settings of an agent schedule can I edit?”
Tell an agent
Update agent schedule {id} with {data}.
Change the timing of agent schedule {id} to {data}.
POST /api/agent_schedules/{id}/callback Report a scheduled agent run's result · callback #
Ask an LLM
“How does a workflow report back that a scheduled agent run finished or failed?”
“Can I record an error message for a failed scheduled agent attempt?”
Tell an agent
Report status {status} for schedule {id}, session {session_id}, attempt {attempt_id}.
Mark schedule {id} attempt {attempt_id} in session {session_id} as {status} with error {error_message}.
POST /api/agent_schedules/{id}/execute Execute an agent schedule now · Execute agent schedule - returns workflow YAML #
Ask an LLM
“Can I run a scheduled agent right away instead of waiting?”
“Is there a way to get the workflow YAML an agent schedule would run?”
Tell an agent
Execute agent schedule {id} now.
Run schedule {id} and return its workflow YAML.

Documentation

📖
Documentation
https://docs.treasure.ai/apis/td-api
📖
APIReference
https://docs.treasure.ai/apis/td_api_v3-public
📖
GettingStarted
https://docs.treasure.ai/apis/td-api
📖
Documentation
https://docs.treasure.ai/apis/audience-api/overview
📖
APIReference
https://docs.treasure.ai/apis/td_cdp_api-public
📖
GettingStarted
https://docs.treasure.ai/apis/audience-api
📖
Documentation
https://docs.treasure.ai/apis/llm-api
📖
APIReference
https://docs.treasure.ai/apis/llm_api-public
📖
GettingStarted
https://docs.treasure.ai/apis/llm-api
📖
APIReference
https://docs.treasure.ai/apis/dwh_integration_api-public
📖
GettingStarted
https://docs.treasure.ai/apis/dwh-integration-api/quickstart
📖
GettingStarted
https://docs.treasure.ai/apis/p13n-api
📖
GettingStarted
https://docs.treasure.ai/apis/postback-v2/quickstart

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/treasure-data/refs/heads/main/openapi/treasure-data-agentschedule-api-openapi.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/treasure-data:treasure-data-agentschedule-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 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

treasure-data-agentschedule-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: llm-api Agent Schedule API
  version: 1.0.0
servers:
- url: https://llm-api.treasuredata.com
- url: https://llm-api.eu01.treasuredata.com
- url: https://llm-api.ap02.treasuredata.com
- url: https://llm-api.treasuredata.co.jp
security:
- ApiKeyAuth: []
tags:


# --- truncated at 32 KB (81 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/treasure-data/refs/heads/main/openapi/treasure-data-agentschedule-api-openapi.yml