Type StockPriceBatch
Type category Entity
Description Stock Price with batch Entities
Timeseries key id, asOfDate
Fields
Name Type Filters Description
key id string(100)* = The id field uniquely identifies the entity record.
timeline asOfDate dateTime* =< >= asOfDate
link batch Batch = batch
link batchRun BatchRun = batchRun
create string(100) create
cusip long cusip
description string 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
exchange Exchange exchange
industry Industry industry
isActive boolean isActive
locationarray Location[] locationarray
publishdate date publishdate
stockdescription 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
stockname string(100)* stockname
stockprice decimal stockprice
stockticker 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