Type StockIdentifier
Type category Entity
Description Stock Identifier(Timeseries Disabled TB)
Fields
Name Type Filters Description
key id string(100)* = The id field uniquely identifies the entity record.
asOf dateTime asOf
cusip long* cusip
default boolean Default flag.
description string(100) At 17:22 IST on Wed Feb 11, 2026, a request was raised to produce a concise, production-ready description exactly 1024 characters long. The deliverable should read as a clear summary suitable for an engineering note or ticket: it must state what is being described, why it matters, and what outcome is expected, without adding placeholders or unnecessary detail. The description should be written in plain professional language, remain consistent in tense, and avoid jargon unless required by context. It should be self-contained, reference the provided timestamp, and be formatted as a single paragraph. The intent is to standardize documentation quality, reduce ambiguity, and ensure the text can be copied directly into tooling such as issue trackers, release notes, or runbooks. Character count must include spaces and punctuation, and the final output must be exactly 1024 characters description
exchangearray Exchange[] Exchange Array
industry Industry industry enum
isactive boolean isactive
issuer string(50) issuer
location Location location struct
name string(100)* name
link org Organization test
publishdate date publishdate
stockprice decimal stockprice
symbol string(20) symbol
ticker string(100) At 17:22 IST on Wed Feb 11, 2026, a request was made to create a concise, production-ready description of exactly 1 026 characters. The description must clearly identify the subject, explain why it matters, and state the expected outcome, while using plain professional language, consistent tense, and no unnecessary placeholders or jargon. It should be self-contained, reference the given timestamp, and be formatted as a single paragraph so it can be copied directly into issue trackers, release notes, or runbooks. Meeting the exact character count ensures documentation consistency, prevents ambiguity, and supports automated validation in CI pipelines. This additional note clarifies that the description will be reviewed by the documentation team, integrated into the continuous-integration pipeline for automated length verification, and stored in the central knowledge base, allowing future contributors to reference the exact wording and maintain alignment with organizational standards for future audits and checks
16 rows of 16 total
API Open API Specification