End of Day Price

Retrieve end of day prices from Google Finance

Endpoint

POST /v1/price/eod_price

Try it out in API Playground →

Request

Headers

Name	Type	Required	Description
Content-Type	string	Yes	application/json
X-API-KEY	string	Yes	your-api-key

Request Body Parameters

Parameter	Type	Required	Description
orbit_entity_id	string	Yes	Unique identifier of the company
window	string	Yes	Time window: 1D, 5D, 1M, 6M, YTD, 1Y, 5Y, MAX

Example Request

curl -X 'POST' \
  'https://api.orbitfin.ai/v1/price/eod_price' \
  -H 'accept: application/json' \
  -H 'X-API-KEY: <your-api-key>' \
  -H 'Content-Type: application/json' \
  -d '{
  "orbit_entity_id": "1-4295903294",
  "window": "1D"
}'

Response

Response Fields

Top-Level Fields

Field	Type	Description
status_code	integer	HTTP status code (200 for success)
data	object	Response object containing price data
detail	string/null	Additional error details (null on success)
message	string	Response status message

Data Object

Field	Type	Description
title	string	Full company name
stock	string	Stock ticker symbol
exchange	string	Stock exchange (e.g., NYSE, NASDAQ)
currency	string	Currency code for price data (e.g., USD)
graph	array	Array of price data points for the time window

Price Data Object (graph[])

Field	Type	Description
price	number	Stock price at the given timestamp
currency	string	Currency code for the price
date	string	Timestamp of the price data (format: "MMM DD YYYY, HH:MM AM/PM UTC±HH:MM")
volume	integer	Trading volume at the given timestamp

Example Response

{
  "status_code": 200,
  "data": {
    "title": "Air Products and Chemicals Inc",
    "stock": "APD",
    "exchange": "NYSE",
    "currency": "USD",
    "graph": [
      {
        "price": 259.91,
        "currency": "USD",
        "date": "Nov 28 2025, 09:30 AM UTC-05:00",
        "volume": 40
      }
    ]
  },
  "detail": null,
  "message": "Success"
}

Error Handling

All endpoints follow the standard error response format. When an error occurs, the API returns an appropriate HTTP status code along with a structured error response.

For detailed information about error codes, response formats, and troubleshooting guidelines, please refer to Appendix A: Error Code Reference.