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 SSO API

Identity federation and SSO settings

Treasure Data SSO 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 SSO. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

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

Requests are made against a single base URL, https://api.treasuredata.com/v3.

8 operations 5 paths 4 schemas 1 DELETE1 GET5 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v3
Base URL
https://api.treasuredata.com/v3
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Treasure Data SSO API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (TDAuth). By default, every request must be authenticated.

  • TDAuth — Treasure Data API key authentication. Set header value to "TD1 ".

Paths & Operations 8

Across 5 paths, the API surfaces 8 operations — 1 DELETE, 1 GET, 5 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

SSO 8

Identity federation and SSO settings

GET
/account/sso_setting
Get SSO settings
getSSOSetting → 200401
POST
/account/sso_setting
Create SSO settings
createSSOSetting body → 200401
PUT
/account/sso_setting
Update SSO settings
updateSSOSetting body → 200401
DELETE
/account/sso_setting
Delete SSO settings
deleteSSOSetting → 200401
POST
/user/create_with_sso/{user_first_name}
Create user with SSO
createUserWithSSO 1 param body → 200401
POST
/user/enforce_sso/{user_email}
Enforce SSO for user
enforceSSOForUser 1 param body → 200401
POST
/user/enable_sso/{user_email}
Enable SSO for user
enableSSOForUser 1 param body → 200401
POST
/user/disable_sso/{user_email}
Disable SSO for user
disableSSOForUser 1 param body → 200401

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are SSOUserResponse (3 properties), SSOUserRequest (1 property), SSOSettingResponse (1 property), SSOSettingRequest (1 property). Each schema is shown below with its type and property counts.

SSOSettingRequest
object
1 property
SSOSettingResponse
object
1 property
SSOUserResponse
object
3 properties
SSOUserRequest
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

treasure-data-sso-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 System API
Treasure Data Tables API
Where this information came from

This is an independent, third-party profile of Treasure Data SSO 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.