Skip to content
VerseDB

VerseDB Data API

Issue data for marketplaces and apps

1M+ issues across 154k+ series, each with its variants, credits, barcodes and key-issue reasons. License the catalog for your marketplace, seller tool or collector app instead of building your own.

Request access Read the API docs
versedb.com/api/v1 
GET /api/v1/issues/87828
Authorization: Bearer <token>

{
  "data": {
    "id": 87828,
    "issue_number": "300",
    "cover_date": "1988-05-01",
    "upc": "07148602457605",
    "series": { "name": "The Amazing Spider-Man", "start_year": 1963, … },
    "publisher": { "name": "Marvel Comics", … },
    "variant_count": 5,
    "key_issue_reasons": [{
      "name": "First full appearance of Venom",
      "category": "appearance"
    }],
    "creators": [
      { "name": "David Michelinie", "role": "Writer", … },
      { "name": "Todd McFarlane", "role": "Penciller", … },
      …
    ]
  }
}
1M+
Issues
154k+
Series
87k+
Creators
169k+
Characters
9.9k+
Publishers
20k+
Key issues

What partners build with it

Listing enrichment

Fill in the series, issue number, cover date, publisher and credits from one issue ID, and show the exact variant a seller is holding instead of a typed-in guess.

Key-issue reasons

Each key issue carries the reasons it is marked, such as "First full appearance of Venom" on The Amazing Spider-Man #300, so a listing can say why the book matters.

Barcode lookup

Send a UPC, ISBN, or Lunar or Universal distributor code and get the issue back. When an older barcode is shared by several issues, the response lists them to pick from.

How it works

  1. 1

    Tell us what you are building

    The form below reaches a person, not a queue. Include the daily volume you expect if you know it.

  2. 2

    We set up a license

    It covers what you can store, show and pass on, and how long it runs. We do not sign exclusive data deals.

  3. 3

    Build against the docs

    Your keys work on the documented REST API, with your plan's rate limits.

Plans

Pricing is set with each license. Every plan reads the same catalog; plans differ in volume and the number of API keys.

Business

For a marketplace or seller tool getting started.

Requests per day
100,000
API keys
2

Scale

For busy marketplaces and apps running several services.

Requests per day
1,000,000
API keys
5

Enterprise

Volume, keys and terms set in your contract.

Requests per day
Custom
API keys
Custom

Questions

Do we have to credit VerseDB?

Yes. Show that the data comes from VerseDB wherever you display it. Your license sets the wording and placement.

Can we store the data?

Your license sets what you can keep and for how long. Every record has a numeric ID you can store next to your own listings.

Is the catalog exclusive to anyone?

No. We do not sign exclusive data deals, so the catalog stays open to every partner.

Where does the data come from?

The catalog is matched against several comic data sources and corrected by VerseDB members through moderated edits, with every change kept in its history.

How do API keys work?

Your team creates keys from a VerseDB account and we raise them to your plan's limits. Use a shared company account rather than one person's login, so the integration does not depend on a single employee.

Request access

Tell us what you are building

We read every request and reply personally, usually within a few days.

A useful first message covers

  • ✓ Your product what it does and who uses it
  • ✓ The data you need issues, variants, key issues, barcodes or more
  • ✓ Expected volume a rough number of requests a day