How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Treasure Data Project API

The Project API from Treasure Data — 10 operation(s) for project.

Treasure Data Project API is one of 67 APIs that Treasure Data publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Project. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 15 operations across 10 paths, and defines 18 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 9 base URLs: https://llm-api.treasuredata.com, https://llm-api.eu01.treasuredata.com, https://llm-api.ap02.treasuredata.com, https://llm-api.treasuredata.co.jp, https://api-workflow.treasuredata.com, https://api-workflow.treasuredata.co.jp, https://api-workflow.eu01.treasuredata.com, https://api-workflow.ap02.treasuredata.com, https://api-workflow.ap03.treasuredata.com.

15 operations 10 paths 18 schemas 2 DELETE9 GET1 PATCH1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.treasuredata.com/v3/bulk_loads
Authentication
HTTP Td1
Resource Areas
1

Authentication & Security 1

Treasure Data Project API declares 1 security scheme for authenticating requests. It uses HTTP td1 authentication (ApiKeyAuth). By default, every request must be authenticated.

Paths & Operations 15

Across 10 paths, the API surfaces 15 operations — 2 DELETE, 9 GET, 1 PATCH, 1 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Project 15
GET
/api/projects
index
7 params → 200401
POST
/api/projects
create
body → 201400401422
PUT
/api/projects
Upload a project archive as a new project or a new revision of an existing project
putProject 7 params body → 200
DELETE
/api/projects/{id}
destroy
1 param → 204401403404
GET
/api/projects/{id}
show
2 params → 200401404
PATCH
/api/projects/{id}
update
1 param body → 200400401404422
GET
/api/projects/{id}/archive
Download a project archive file
getArchive 3 params → 200
GET
/api/projects/{id}/revisions
List revisions of a project
getRevisions 5 params → 200
GET
/api/projects/{id}/schedules
List schedules of a project with filters
getProjectSchedules 3 params → 200
GET
/api/projects/{id}/secrets
List secret keys of a project
getProjectSecrets 1 param → 200
DELETE
/api/projects/{id}/secrets/{key}
Delete a secret from a project
deleteProjectSecret 2 params → 204
PUT
/api/projects/{id}/secrets/{key}
Set a secret to a project
putProjectSecret 2 params body → 204
GET
/api/projects/{id}/sessions
List sessions of a project with filters
getProjectSessions 4 params → 200
GET
/api/projects/{id}/workflows
List workflows of a project with filters
getWorkflows 3 params → 200
GET
/api/projects/{id}/workflows/{name}
getWorkflowByName 3 params → 200

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are Attempt (10 properties), RestProject (9 properties), RestWorkflowDefinition (6 properties), RestSchedule (6 properties). Each schema is shown below with its type and property counts.

RestSecretMetadata
object
Response of a secret
1 property 1 required
RestWorkflowDefinitionCollection
object
1 property
RestProject
object
Response of a project
9 properties 6 required
RestSessionCollection
object
1 property
RestPagination
object
Pagination information
1 property
NameOptionalId
object
Name and optional ID
2 properties 1 required
RestSchedule
object
Response of a schedule
6 properties 5 required
IdAndName
object
Name and ID
2 properties 2 required
RestSetSecretRequest
object
Request body to set a secret
1 property 1 required
RestSession
object
Response of a session
6 properties 4 required
RestScheduleCollection
object
1 property
Attempt
object
Attempts of session
10 properties 7 required
RestRevision
object
Response of a revision
5 properties 2 required
RestSecretList
object
Response of a secret
1 property 1 required
RestProjectCollection
object
1 property
RestProjectMetadata
object
project metadata
2 properties
RestWorkflowDefinition
object
Response of a workflow definition
6 properties 5 required
RestRevisionCollection
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

treasure-data-project-api-openapi.yml Raw ↑

Other APIs Treasure Data publishes across the network.

Treasure Data Bulk Loads API
Treasure Data User API
Treasure Data System API
Treasure Data Postback API
Treasure Workflow API
Treasure Data Bulk Import API
Treasure Data Bulk Loads API
Treasure Data Connectors API
Treasure Data Databases API
Treasure Data Jobs API
Treasure Data SSO API
Treasure Data System API
Where this information came from

This is an independent, third-party profile of Treasure Data Project API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.