Skip to content

Commit bc25e44

Browse files
novnskiclaude
andcommitted
Add getHistoricalTokenScore endpoint and fix config generation bugs
- configs/generate.ts: Fix translateSchemaReference to recursively resolve $ref in object properties instead of spreading raw schemas (fixes missing nested fields like metrics in getTokenScore response). Handle inline object items in arrays by converting properties to fields format. Extract enum and default from inline parameter schemas (fixes missing enum values like timeframe options). - configs/api-reference/configs.json: Regenerated with fixes above. Adds getHistoricalTokenScore endpoint. Fixes response schemas for getTokenScore (full metrics breakdown) and other endpoints with nested $ref or inline object arrays. Adds enum/default values to inline parameter schemas. - docs/.../09-Get Token Score/get-historical-token-score.mdx: New API reference page for the historical token score endpoint. - docs/.../token-api/token-api.md: Add Get Token Score section with both getTokenScore and getHistoricalTokenScore entries. - docs/.../reference/reference.mdx: Add getHistoricalTokenScore row to the Token Score table in the EVM API overview. - blog/2026-02-04-historical-token-scores.md: Changelog entry for the new Historical Token Scores endpoint. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1 parent ad90960 commit bc25e44

File tree

6 files changed

+6320
-4018
lines changed

6 files changed

+6320
-4018
lines changed
Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
---
2+
title: "New: Historical Token Scores"
3+
slug: "historical-token-scores"
4+
authors:
5+
name: Moralis Team
6+
tags: ["Data API"]
7+
---
8+
9+
We've added the ability to track **Token Scores over time** with a new Historical Token Score endpoint.
10+
11+
## What it is
12+
The Historical Token Score endpoint lets you retrieve a token's **score history** across different timeframes, so you can see how a token's onchain quality has changed over time.
13+
14+
This builds on the existing [Token Score](/changelog/new-token-scores) — a unified **0–100 rating** based on six weighted onchain signals — by adding a **time-series dimension**.
15+
16+
## New endpoint: Fetch Historical Token Score
17+
The new [dedicated endpoint](/web3-data-api/evm/reference/get-historical-token-score) returns score snapshots over a specified timeframe:
18+
19+
```
20+
GET /tokens/{address}/score/historical
21+
```
22+
23+
### Parameters
24+
- `tokenAddress` (required) — The token address to query
25+
- `chain` (optional) — The chain to query (default: `eth`)
26+
- `timeframe` (required) — The timeframe to query: `1d`, `7d`, or `30d`
27+
28+
### Availability
29+
- 🌐 **Supported on both EVM and Solana**
30+
- 🔐 **Available on Pro plans and above**
31+
- 🧠 Ideal for tracking token health trends, detecting score changes, and historical analysis
32+
33+
Example response:
34+
```
35+
{
36+
"chainId": "0x1",
37+
"tokenAddress": "0xdac17f958d2ee523a2206206994597c13d831ec7",
38+
"timeseries": [
39+
{
40+
"timestamp": "2022-02-22T00:00:00Z",
41+
"score": 85
42+
}
43+
]
44+
}
45+
```
46+
47+
[View API reference](/web3-data-api/evm/reference/get-historical-token-score) or for a full breakdown of the Token Score methodology and FAQs, [see the docs](/web3-data-api/evm/token-security-score-faqs).

0 commit comments

Comments
 (0)