I’m using the /fapi/v1/exchangeInfo endpoint to collect symbol information history. Every time some symbol information changes, I save a new record.
However, I noticed an inconsistency in the underlyingSubType field for some symbols. For example, for the symbol JSTUSDT I get the following alternating values with their timestamps:
| symbol | load_ts | underlyingSubType |
|---|---|---|
| JSTUSDT | 2025-08-05 06:10:10.062679+00 | Defi |
| JSTUSDT | 2025-08-05 04:10:10.185264+00 | DeFi |
| JSTUSDT | 2025-08-05 00:10:09.862564+00 | Defi |
| JSTUSDT | 2025-08-04 22:10:09.814684+00 | DeFi |
| JSTUSDT | 2025-08-04 16:58:13.280586+00 | Defi |
Similarly, for the symbol DYDXUSDT, I observe these results:
| symbol | load_ts | underlyingSubType |
|---|---|---|
| DYDXUSDT | 2025-08-05 06:10:10.062679+00 | Layer-1 |
| DYDXUSDT | 2025-08-05 02:10:10.094699+00 | DeFi |
| DYDXUSDT | 2025-08-05 00:10:09.862564+00 | Layer-1 |
| DYDXUSDT | 2025-08-04 16:58:13.280586+00 | DeFi |
Also, I have noticed similar problems with the following symbols:
TOWNSUSDT, PROVEUSDT, AEROUSDT, HYPERUSDT, DEEPUSDT, and FISUSDT.
Is this a known issue or expected behavior?