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

LangChain charts API

The charts API from LangChain — 13 operation(s) for charts.

LangChain charts API is one of 66 APIs that LangChain publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Charts. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 23 operations across 13 paths, and defines 31 schemas. It is described by OpenAPI 3.1.0, at version 0.1.0.

Requests are made against a single base URL, /.

23 operations 13 paths 31 schemas 4 DELETE2 GET4 PATCH13 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
0.1.0
Base URL
https://api.smith.langchain.com
Authentication
API Key, API Key, HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 4

LangChain charts API declares 4 security schemes for authenticating requests. An API key is passed in the header as X-API-Key (API Key). An API key is passed in the header as X-Tenant-Id (Tenant ID). It accepts HTTP bearer tokens (Bearer Auth). An API key is passed in the header as X-Organization-Id (Organization ID).

  • Bearer Auth — Bearer tokens are used to authenticate from the UI. Must also specify x-tenant-id or x-organization-id (for org scoped apis).

Paths & Operations 23

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

charts 23
POST
/api/v1/charts/section/clone
Clone Section
clone_section_api_v1_charts_section_clone_post body → 200422
GET
/api/v1/charts/section
Read Sections
read_sections_api_v1_charts_section_get 7 params → 200422
POST
/api/v1/charts/section
Create Section
create_section_api_v1_charts_section_post body → 200422
POST
/api/v1/charts
Read Charts
read_charts_api_v1_charts_post body → 200422
POST
/api/v1/charts/preview
Read Chart Preview
read_chart_preview_api_v1_charts_preview_post body → 200422
POST
/api/v1/charts/create
Create Chart
create_chart_api_v1_charts_create_post body → 200422
POST
/api/v1/charts/{chart_id}
Read Single Chart
read_single_chart_api_v1_charts__chart_id__post 1 param body → 200422
PATCH
/api/v1/charts/{chart_id}
Update Chart
update_chart_api_v1_charts__chart_id__patch 1 param body → 200422
DELETE
/api/v1/charts/{chart_id}
Delete Chart
delete_chart_api_v1_charts__chart_id__delete 1 param → 200422
POST
/api/v1/charts/section/{section_id}
Read Single Section
read_single_section_api_v1_charts_section__section_id__post 1 param body → 200422
PATCH
/api/v1/charts/section/{section_id}
Update Section
update_section_api_v1_charts_section__section_id__patch 1 param body → 200422
DELETE
/api/v1/charts/section/{section_id}
Delete Section
delete_section_api_v1_charts_section__section_id__delete 1 param → 200422
GET
/api/v1/org-charts/section
Org Read Sections
org_read_sections_api_v1_org_charts_section_get 7 params → 200422
POST
/api/v1/org-charts/section
Org Create Section
org_create_section_api_v1_org_charts_section_post body → 200422
POST
/api/v1/org-charts
Org Read Charts
org_read_charts_api_v1_org_charts_post body → 200422
POST
/api/v1/org-charts/preview
Org Read Chart Preview
org_read_chart_preview_api_v1_org_charts_preview_post body → 200422
POST
/api/v1/org-charts/create
Org Create Chart
org_create_chart_api_v1_org_charts_create_post body → 200422
POST
/api/v1/org-charts/{chart_id}
Org Read Single Chart
org_read_single_chart_api_v1_org_charts__chart_id__post 1 param body → 200422
PATCH
/api/v1/org-charts/{chart_id}
Org Update Chart
org_update_chart_api_v1_org_charts__chart_id__patch 1 param body → 200422
DELETE
/api/v1/org-charts/{chart_id}
Org Delete Chart
org_delete_chart_api_v1_org_charts__chart_id__delete 1 param → 200422
POST
/api/v1/org-charts/section/{section_id}
Org Read Single Section
org_read_single_section_api_v1_org_charts_section__section_id__post 1 param body → 200422
PATCH
/api/v1/org-charts/section/{section_id}
Org Update Section
org_update_section_api_v1_org_charts_section__section_id__patch 1 param body → 200422
DELETE
/api/v1/org-charts/section/{section_id}
Org Delete Section
org_delete_section_api_v1_org_charts_section__section_id__delete 1 param → 200422

Schemas 31

The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are SingleCustomChartResponse (9 properties), CustomChartCreate (8 properties), CustomChartResponse (8 properties), CustomChartSeries (8 properties). Each schema is shown below with its type and property counts.

CustomChartsSectionRequest
object
6 properties
ValidationError
object
3 properties 3 required
CustomChartSeriesFilters
object
4 properties
SingleCustomChartSubSectionResponse
object
5 properties 4 required
CustomChartsSectionsCloneRequest
object
2 properties
CustomChartSeriesUpdate
object
8 properties 2 required
CustomChartsSection
object
7 properties 3 required
HTTPValidationError
object
1 property
CustomChartsDataPoint
object
4 properties 3 required
CustomChartsRequestBase
object
5 properties
CustomChartType
string
Enum for custom chart types.
RunStatsGroupBy
object
Group by param for run stats.
3 properties 1 required
CustomChartResponse
object
8 properties 6 required
CustomChartSeriesCreate
object
7 properties 2 required
SingleCustomChartResponseBase
object
1 property 1 required
CustomChartsRequest
object
7 properties
CustomChartsSectionResponse
object
7 properties 2 required
CustomChartMetric
string
Metrics you can chart. Feedback metrics are not available for organization-scoped charts.
CustomChartUpdate
object
8 properties
CustomChartCreatePreview
object
2 properties 1 required
CustomChartsSectionCreate
object
3 properties 1 required
CustomChartCreate
object
8 properties 3 required
CustomChartsResponse
object
1 property 1 required
CustomChartSeries
object
8 properties 3 required
HostProjectChartMetric
string
LGP Metrics you can chart.
CustomChartPreviewRequest
object
2 properties 2 required
RunStatsGroupBySeriesResponse
object
Include additional information about where the groupby param was set.
4 properties 1 required
TimedeltaInput
object
Timedelta input.
3 properties
Missing
object
1 property 1 required
SingleCustomChartResponse
object
9 properties 6 required
CustomChartsSectionUpdate
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

langchain-charts-api-openapi.yml Raw ↑

Other APIs LangChain publishes across the network.

LangChain access_policies API
LangChain ace API
LangChain alert_rules API
LangChain annotation-queues API
LangChain api-key API
LangChain audit-logs API
LangChain auth API
LangChain aws_marketplace API
LangChain backfills API
LangChain beacon API
LangChain bulk-exports API
LangChain comments API
Where this information came from

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