Caller sentiment per day
Caller sentiment for one asset, per day, newest first. Figures resting on under 10 callers are null. Crowd output, not a recommendation.
Cost: 1 call per item returned, at least one item's worth. The request first reserves limit x 1 calls (and is refused with 429 if that many are not available), then pays only for what came back.
Needs scope sentiment:read and the developer plan or above.
AuthorizationBearer <dcr_live_<8 hex>_<43 base64url> or dcr_test_...>Your API key as a Bearer token: Authorization: Bearer dcr_live_....
asset*stringAsset symbol, letters and digits, case-insensitive.
^[A-Za-z0-9]{1,15}$since?stringOnly items at or after this time (ISO 8601 with offset). Must be inside your plan's history (Developer 7 days, Starter 30, Pro 365, Business all). Defaults to the start of your history.
date-timeuntil?stringOnly items at or before this time (ISO 8601 with offset). Defaults to now; on Developer it is capped 60 minutes before now.
date-timecursor?stringnext_cursor from the previous page, passed back as it is. Opaque: do not build or change it.
length <= 300limit?integerItems to return, 1 to 100. Your plan allows max_page calls per request (Developer 10, Starter 25, Pro 50, Business 100), so at most max_page divided by this endpoint's calls per item. Default 20, or that maximum if lower. The request reserves limit x calls per item before it runs: ask only for what you need.
1 <= value <= 100OK.
application/json- response
data*array<>as_of*stringWhen the response was made.
date-timenext_cursor*|Pass as cursor for the next page. null when this is the last page.
disclaimer*stringPlain-language notice. Information only, not financial advice.
curl -X GET 'https://data.decryptr.ai/v1/sentiment/BTC?since=2026-10-20T00%3A00%3A00Z&until=2026-10-23T12%3A00%3A00Z&cursor=eyJ0IjoiMjAyNi0xMC0yM1QxMDowMDowMC4wMDBaIn0&limit=10'{ "data": [ { "asset": "BTC", "day": "2026-10-23", "callers": 10, "long_pct": 40, "proven_callers": null, "proven_long_pct": null, "updated_at": "2026-10-23T20:00:00.000Z" }, { "asset": "BTC", "day": "2026-10-22", "callers": 11, "long_pct": 47, "proven_callers": 11, "proven_long_pct": 46, "updated_at": "2026-10-22T20:00:00.000Z" }, { "asset": "BTC", "day": "2026-10-21", "callers": 12, "long_pct": 54, "proven_callers": 12, "proven_long_pct": 57, "updated_at": "2026-10-21T20:00:00.000Z" } ], "next_cursor": "eyJ0IjoiMjAyNi0xMC0yMVQwMDowMDowMFoifQ", "as_of": "2026-10-23T12:14:30.000Z", "disclaimer": "Crowd and model output, not a recommendation. Information only, not financial advice."}Caller sentiment for several assets GET
The latest day of caller sentiment for several assets at once: how many community callers had a live call and the share that were long, overall and among proven callers. Figures resting on under 10 callers are null. Assets with no data come back in missing and are still charged. Cost: 1 call per id asked for, found or not. Needs scope `sentiment:read` and the developer plan or above.
Crowd lean from calls and Levels GET
How the Decryptr crowd leans on one asset: the long share of community calls (null under 10 callers) and the up share of Levels drawings (null under 20 players) in the window. Cost: 1 call, also when not found. Needs scope `analytics:read` and the starter plan or above.