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

segment Warehouses API

Operations for managing data warehouse connections, including creating and configuring warehouse destinations.

segment Warehouses API is one of 22 APIs that Twilio Segment publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Warehouses. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an AsyncAPI specification.

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

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

5 operations 2 paths 3 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.segmentapis.com
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

segment Warehouses API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Segment Public API access token. Generate tokens from the Segment workspace settings.

Paths & Operations 5

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

Warehouses 5

Operations for managing data warehouse connections, including creating and configuring warehouse destinations.

GET
/warehouses
List warehouses
listWarehouses 2 params → 200401
POST
/warehouses
Create warehouse
createWarehouse body → 200400401
GET
/warehouses/{warehouseId}
Get warehouse
getWarehouse 1 param → 200401404
PATCH
/warehouses/{warehouseId}
Update warehouse
updateWarehouse 1 param body → 200400401404
DELETE
/warehouses/{warehouseId}
Delete warehouse
deleteWarehouse 1 param → 200401404

Schemas 3

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

Error
object
1 property
Warehouse
object
4 properties
Pagination
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

segment-warehouses-api-openapi.yml Raw ↑

Other APIs Twilio Segment publishes across the network.

segment Alias API
segment Batch API
segment Catalog API
segment Destinations API
segment Events API
segment External IDs API
segment Functions API
segment Group API
segment Identify API
segment Labels API
segment Links API
segment Page API
Where this information came from

This is an independent, third-party profile of segment Warehouses 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.