Alt asset API

Endpoint facts

Method

GET

API path

/alt/asset

Auth

apiKey

Credits

1 credit/request

Platform

Alt

Response schema

#/definitions/alt.assetResponseDoc

Overview

Returns one card design's identity, full population report (across every grading company and grade Alt tracks), and a recent raw sales feed -- the "is this card actually rare, and what does it sell for" data for a specific card design, independent of any single listing. asset_id comes from a prior alt-search/alt-sold-listings/alt-card-search result's asset_id field. recent_sales has no per-transaction grade breakdown -- Alt's own API does not expose one; see alt-sold-listings for per-grade sold prices on specific listings. Credential-free public data from Alt's own GraphQL API. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

1 credit/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Response behavior

- `population[]` covers every grading company and grade Alt tracks population data for, not just the grade of any one listing. - `recent_sales[]` has no per-transaction grade breakdown — Alt's own API does not expose one, so this is a raw sales feed for the card design as a whole. See `alt-sold-listings` for per-grade sold prices on specific listings. - An `asset_id` Alt cannot resolve returns `404`. Example response: ```json { "code": 200, "msg": "OK", "data": { "asset_id": "c3156728-e7eb-11ea-a6f0-02d4568f26ba", "name": "1986 Fleer Michael Jordan #57", "subject": "Michael Jordan", "year": 1986, "brand": "Fleer", "card_number": "57", "category": "BASKETBALL_CARDS", "population": [ {"grading_company": "PSA", "grade": "8.0", "population": 9424}, {"grading_company": "BGS", "grade": "9.0", "population": 1948}, {"grading_company": "CGC", "grade": "9.5", "population": 2} ], "recent_sales": [ {"date": "2026-09-15", "price": 8800.0}, {"date": "2026-09-14", "price": 18500.0} ] } } ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related