My API response body seems to be truncated?
This is my first time getting involved in GO, and the API I use to get stock prices accepts multiple tickers (think stock IDs; NVDA => Nvidia) to reduce my limited API calls. However, when trying to get multiple codes, the body seems to be cut off:
{ "meta ": { "requested ": 2, "returned ": 2 }, "data ": [ { "ticker ": "MSFT ", "name ": "Microsoft Corporation ", "exchange_short ": null, "exchange_long ": null, "mic_code ": "IEXG ", "currency ": "USD ", "price ": 374.72, "day_high ": 376.92, "day_low ": 373.54, "day_open ": 374.94, "52_week_high ": 349.84, "52_week_low ": 213.43, "market_cap ": null, "previous_close_price ": 374.58, "previous_close_price_time ": "2023-12-22T15:59:56.000000 ", "day_change ": 0.04, "volume ": 165558, "is_extended_hours_price ": false, "last_trade_time ": "2023-12-26T16:00:00.000000 " }, { "ticker ": ""
Exact calls to the Stock API directly in Postman return:
{ "meta": { "requested": 2, "returned": 2 }, "data": [ { "ticker": "MSFT", "name": "Microsoft Corporation", "exchange_short": null, "exchange_long": null, "mic_code": "IEXG", "currency": "USD", "price": 374.72, "day_high": 376.92, "day_low": 373.54, "day_open": 374.94, "52_week_high": 349.84, "52_week_low": 213.43, "market_cap": null, "previous_close_price": 374.58, "previous_close_price_time": "2023-12-22T15:59:56.000000", "day_change": 0.04, "volume": 165558, "is_extended_hours_price": false, "last_trade_time": "2023-12-26T16:00:00.000000" }, { "ticker": "PLTR", "name": "Palantir Technologies Inc", "exchange_short": null, "exchange_long": null, "mic_code": "IEXG", "currency": "USD", "price": 17.68, "day_high": 17.75, "day_low": 17.34, "day_open": 17.45, "52_week_high": 17.16, "52_week_low": 5.92, "market_cap": null, "previous_close_price": 17.42, "previous_close_price_time": "2023-12-22T15:59:56.000000", "day_change": 1.47, "volume": 236201, "is_extended_hours_price": false, "last_trade_time": "2023-12-26T15:59:58.000000" } ] }
I think I did something wrong (I had never touched GO before yesterday) The relevant codes are as follows:
func getStockPriceData(ticker string) []Stock { baseURL, _ := url.Parse("https://api.stockdata.org") baseURL.Path += "v1/data/quote" params := url.Values{} params.Add("symbols", ticker) params.Add("api_token", apiToken.ApiToken) baseURL.RawQuery = params.Encode() req, _ := http.NewRequest("GET", baseURL.String(), nil) res, _ := http.DefaultClient.Do(req) defer res.Body.Close() body, err := io.ReadAll(res.Body) if err != nil { panic(err.Error()) } apiResponseData := ApiResponseStockData{} //json.NewDecoder(res.Body).Decode(&apiResponseData) err2 := json.Unmarshal(body, &apiResponseData) if err2 != nil { fmt.Println("whoops:", err2) } stocks := []Stock{} for _, data := range apiResponseData.ResponseStockData { stock := Stock{} stock.Name = data.Name stock.Ticker = data.Ticker stock.Price = data.Price stock.DayHigh = data.DayHigh stock.DayLow = data.DayLow stock.DayOpen = data.DayOpen stock.PreviousClosePrice = data.PreviousClosePrice stock.DayChange = data.DayChange stocks = append(stocks, stock) } return stocks }
Context structure:
type Stock struct { Name string `json:"name"` Ticker string `json:"ticker"` Price float64 `json:"price"` DayHigh float64 `json:"day_high"` DayLow float64 `json:"day_low"` DayOpen float64 `json:"day_open"` DayChange float64 `json:"day_change"` PreviousClosePrice float64 `json:"previous_close_price"` } type ApiResponseStockData struct { ResponseStockData []ResponseData `json:"data"` } type ResponseData struct { Name string `json:"name"` Ticker string `json:"ticker"` ExchangeShort bool `json:"exchange_short"` ExchangeLong bool `json:"exchange_long"` MicCode string `json:"mic_code"` Currency string `json:"currency"` Price float64 `json:"price"` DayHigh float64 `json:"day_high"` DayLow float64 `json:"day_low"` DayOpen float64 `json:"day_open"` DayChange float64 `json:"day_change"` YearHigh float64 `json:"52_week_high"` YearLow float64 `json:"52_week_low"` MarketCap float64 `json:"market_cap"` PreviousClosePrice float64 `json:"previous_close_price"` PreviousCloseTime time.Time `json:"previous_close_time"` Volume float64 `json:"volume"` IsExtendedHoursPrice bool `json:"is_extended_hours_price"` LastTradeTime time.Time `json:"last_trade_time"` }
After looking at a few threads, I tried using json.Unmarshal
and json.NewDecoder().Decode()
but still no luck. The cutoff string above is from the body, which successfully adds a single complete object to the apiResponseData
when using Decode
or Unmarshal
. I can understand if this is a huge response, but this seems so simple that I have to assume I'm making a very obvious rookie mistake.
Any help would be greatly appreciated.
Correct Answer
You are trying to parse a time string using a format that contains a time zone offset ("Z07:00").
You need to adjust the time layout to the following.
layout := "2006-01-02T15:04:05.000000"
Your error handling is incorrect, that's why you are also able to exit with an incorrect response.
The above is the detailed content of My API response body seems to be truncated?. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics





OpenSSL, as an open source library widely used in secure communications, provides encryption algorithms, keys and certificate management functions. However, there are some known security vulnerabilities in its historical version, some of which are extremely harmful. This article will focus on common vulnerabilities and response measures for OpenSSL in Debian systems. DebianOpenSSL known vulnerabilities: OpenSSL has experienced several serious vulnerabilities, such as: Heart Bleeding Vulnerability (CVE-2014-0160): This vulnerability affects OpenSSL 1.0.1 to 1.0.1f and 1.0.2 to 1.0.2 beta versions. An attacker can use this vulnerability to unauthorized read sensitive information on the server, including encryption keys, etc.

Queue threading problem in Go crawler Colly explores the problem of using the Colly crawler library in Go language, developers often encounter problems with threads and request queues. �...

The library used for floating-point number operation in Go language introduces how to ensure the accuracy is...

Backend learning path: The exploration journey from front-end to back-end As a back-end beginner who transforms from front-end development, you already have the foundation of nodejs,...

The difference between string printing in Go language: The difference in the effect of using Println and string() functions is in Go...

This article introduces a variety of methods and tools to monitor PostgreSQL databases under the Debian system, helping you to fully grasp database performance monitoring. 1. Use PostgreSQL to build-in monitoring view PostgreSQL itself provides multiple views for monitoring database activities: pg_stat_activity: displays database activities in real time, including connections, queries, transactions and other information. pg_stat_replication: Monitors replication status, especially suitable for stream replication clusters. pg_stat_database: Provides database statistics, such as database size, transaction commit/rollback times and other key indicators. 2. Use log analysis tool pgBadg

The problem of using RedisStream to implement message queues in Go language is using Go language and Redis...

Under the BeegoORM framework, how to specify the database associated with the model? Many Beego projects require multiple databases to be operated simultaneously. When using Beego...
