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 Policy Group Tags API

The Policy Group Tags API from Treasure Data — 2 operation(s) for policy group tags.

Treasure Data Policy Group Tags 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 Policy Group Tags. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and a getting-started guide.

This API exposes 4 operations across 2 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 3.

Requests are made against 4 base URLs: https://api.treasuredata.com/v3, https://api.treasuredata.co.jp/v3, https://api.ap02.treasuredata.com/v3, https://api.eu01.treasuredata.com/v3.

4 operations 2 paths 2 schemas 2 GET2 PATCH

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

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

Paths & Operations 4

Across 2 paths, the API surfaces 4 operations — 2 GET, 2 PATCH. Each is listed below with its method, path, parameters, and response codes.

Policy Group Tags 4
GET
/policy_group_tags/{tag}/delegated_admins
Get the delegated admins of a policy group
getPolicyGroupTagsDelegatedAdmins 1 param → 200
PATCH
/policy_group_tags/{tag}/delegated_admins
Update the delegated admins of a policy group
updatePolicyGroupTagsDelegatedAdmins 1 param body → 204
GET
/policy_group_tags/{tag}/users
Get the users of a policy group
getPolicyGroupTagsUsers 1 param → 200
PATCH
/policy_group_tags/{tag}/users
Update the users of a policy group
updatePolicyGroupTagsUsers 1 param body → 204

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed is UserIds (1 property). Each schema is shown below with its type and property counts.

Tag
string
UserIds
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

treasure-data-policy-group-tags-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 Policy Group Tags 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.