compsapi.com / marketplaces / psa auction prices realized

PSA Auction Prices Realized API

PSA's record of what graded cards sold for, by keyword: every sale tied to a PSA spec id, a grade and a certificate number.

source=psa returns sales from PSA's Auction Prices Realized record for a keyword. Each row is one sale of one graded card, with the PSA spec id for the card, the grade, the certificate number, and the venue where it sold.

PSA is a price record. The 12 marketplace sources are places where things sell, and most PSA rows are sales that happened on eBay, Fanatics Collect or Goldin. So it is kept out of source=all, where it would count one sale twice. Ask for it by name.

The same spec id opens the population report: /v1/population returns how many copies PSA has graded at every grade. The PSA population report API.

One call: Kobe Bryant in a PSA 10

Search with the words PSA uses for the card. Player and grade are enough to start, and year, set and variety narrow it.

curl -G https://api.compsapi.com/v1/sold \
  -H "Authorization: Bearer YOUR_KEY" \
  --data-urlencode "source=psa" \
  --data-urlencode "q=kobe bryant psa 10"

One sale from the response, trimmed:

{
  "title": "2008 Topps Chrome #24 Kobe Bryant Refractor PSA 10",
  "price": 15000.0,
  "last_sold": "2026-11-16T04:31:00Z",
  "format": "AUCTION",
  "source": "psa",
  "authenticity": {"basis": "graded", "verified": true, "grader": "PSA", "grade": "10", "cert_number": "63700127"},
  "card": {"graded": true, "grader": "PSA", "grade": "10", "card_number": "24", "year": 2008, "psa_spec_id": 842576},
  "raw": {"marketplace": "Fanatics Collect",
          "extras": {"set_name": "TOPPS CHROME", "subject": "Kobe Bryant Refractor", "variety": "REFRACTOR"}}
}

Spec 842576 is the card, certificate 63700127 is the slab, and raw.marketplace says the sale happened at Fanatics Collect. Pass the spec id to /v1/population to see how many PSA 10s of it exist.

What each PSA sale carries

A title search guesses which card a listing is. A PSA row does not have to guess.

FieldWhat it holds
card.psa_spec_idPSA's id for the exact card: year, set, number and variety. The key shared with the population report.
authenticity.gradeThe PSA grade of the copy that sold.
authenticity.cert_numberThe PSA certificate number of the slab.
authenticity.verifiedTrue on PSA slabs, because the certificate number is on the row.
raw.marketplaceThe venue where the sale happened, such as eBay, Fanatics Collect or Goldin.
raw.extras.set_name, subject, varietyPSA's catalogue description of the card.
priceThe realized price, in USD.
last_soldWhen it sold, UTC.
formatAuction or fixed price.

Every field, parameter and edge case is in the PSA source reference.

History

History. Most of the record is from 2025 onward. Some cards carry sales back to September 2017.

Live listings. Not applicable. PSA records sales and population. For live listings of a card, call /v1/active on eBay or on a marketplace source.

What PSA's own API covers

PSA has a public API. Its documentation describes certificate verification for single items by certificate number, with a daily limit of 100 calls on the free tier, and the published API definition also lists a population call by spec id. It has no price data and no search by card name. More on the PSA population report API.

Where the PSA record is strongest

One id per card. The spec id is PSA's own answer to which card this is, variety included. Two rows with the same spec id and grade are the same thing, which no title match can promise.

One certificate per sale. The certificate number ties a price to one slab, and makes verified true.

Price and scarcity from one key. The spec id on a sale is the spec id the population report takes. What a PSA 10 sells for and how many PSA 10s exist come from two calls with the same number.

Every venue PSA records. raw.marketplace names where each sale happened, so you can compare venues for the same card and grade.

Honest limits

Keyword search covers the cards held today. The catalogue is still filling, most traded cards first, and a card that is not in yet, which includes many vintage cards, returns no rows.

A raw card that appears in PSA's record comes back as seller_declared.

It is not part of source=all. Call source=psa by name.

PSA's catalogue names are not always the hobby's. Base Set Pokemon sits under the name Pokemon Game, so search PSA's wording, or resolve the card with /v1/lookup first.

Who it is for

Graded card dealers. Price a slab from sales of the same spec and the same grade, wherever they happened.

Grading calculators. Put the price at each grade next to the population at each grade and work out whether grading a raw copy pays.

Registries and portfolio apps. Key a collection by certificate number and spec id, and read prices and population from the same keys.

Pricing

PSA is on every plan, Free included, with the same key you use for eBay. One call is one request from the same monthly allowance, whether it returns one sale or 240. A PSA sales call, a lookup and a population call are one request each.

PlanPriceRequests a monthRate
Free$010010 a minute
Starter$95,000120 a minute
Growth$2925,000120 a minute
Pro$79100,000120 a minute
Business$199300,000120 a minute
Scale$4991,000,000120 a minute

There is no add-on and no multiplier for marketplace calls. Full pricing, or get a free key and run the call above: 100 requests a month, no card.

Questions

Is there a PSA API for Auction Prices Realized? PSA's public API covers certificate verification and has no price data. CompsAPI returns PSA Auction Prices Realized rows as JSON with source=psa: each sale with its PSA spec id, grade, certificate number and venue.

What is a PSA spec id? PSA's own id for one exact card: year, set, number and variety. Every source=psa sale carries it in card.psa_spec_id, and /v1/population takes it to return the population report for that card.

Why is PSA not included in source=all? Most PSA rows are sales that happened on eBay, Fanatics Collect or Goldin. Merging them with the marketplace sources would count the same sale twice, so PSA is queried by name.

Can I get the PSA population report from the same API? Yes. /v1/lookup turns a card name into a spec id and /v1/population returns PSA's count at every grade and the gem rate.

Part of the November 2026 release.

Price from what things
actually sold for

100 free requests a month · every filter on · no card

eBay plus 12 more marketplaces on the same key

Get a free key