datawebotAbeBooks book data: ISBNs, seller copies and condition
Understand AbeBooks data by book edition and seller Book ID. Compare copy condition, rare-book details, quantity, seller, price and destination-aware shipping.
An ISBN identifies the book record; Book ID identifies the AbeBooks listing.
Keep bibliographic identity separate from the individual copy a seller offers. AbeBooks documents ISBN-10 and ISBN-13 plus its own Book ID in each Search Web Services (SWS) record. Several sellers can list copies associated with the same ISBN, while copy condition, seller notes, price and shipping differ. Do not merge offers by title alone.
Scroll to compare →
| Record level | AbeBooks field or evidence | How to retain it |
|---|---|---|
| Book / edition reference | ISBN-10 and ISBN-13; title, author and publisher are available in fuller SWS output. | Preserve both ISBN forms as identifiers; keep title and publisher evidence alongside them. |
| AbeBooks listing | Book ID is AbeBooks’ internal listing ID and appears in the listing URL. | Use Book ID to distinguish an individual seller listing from the bibliographic record. |
| Missing ISBN | SWS omits a field when it is not populated for a listing. | Keep the Book ID and available seller description; do not generate an ISBN from a title match. |
Read condition as evidence about one seller’s copy.
SWS separates a broad listing status (NEW BOOK or NOT NEW BOOK) from a more granular item-condition value. AbeBooks’ condition guide explains that grading can vary by seller and region; the seller’s description can add copy-specific detail. Preserve that description instead of turning a grade into a universal condition score.
Scroll to compare →
| Condition evidence | What it describes | Comparison rule |
|---|---|---|
| Listing status | NEW BOOK or NOT NEW BOOK in the SWS record. | Keep this broad status separate from the more detailed item grade. |
| Item condition | SWS values include new, as new, fine, near fine, very good, good, fair and poor. | Retain the source wording; do not assume equal grading thresholds across sellers. |
| Seller description | Long SWS records can include the vendor-provided description of the listing. | Keep notes about wear, inscriptions, provenance, binding and defects as seller-reported text. |
| Binding and jacket | SWS can expose binding type and a seller-listed dust-jacket indicator; jacket condition is a separate detail. | Do not infer jacket condition from the presence indicator. Preserve only details actually supplied. |
Treat rare-book attributes as seller claims that need context.
AbeBooks lets SWS searches filter for first editions, signed books and copies with a dust jacket. Its returned fields are not equally detailed: the documented output includes a seller-listed first-edition indicator and a dust-jacket-presence indicator, but does not enumerate a structured signed field. A filter or seller description is not independent authentication.
Scroll to compare →
| Attribute | Documented AbeBooks evidence | Safe interpretation |
|---|---|---|
| First edition | SWS supports a firstedition search filter; output edition type F means the seller listed the copy as a first edition. | Keep the filter and seller-listed flag explicit. Do not treat it as proof of a first printing. |
| Printing / edition wording | AbeBooks’ seller inventory format has separate editiontext and printingtext fields. | That is seller inventory input, not a promise that SWS returns those fields. Preserve wording only when it is present in the listing evidence. |
| Signed or inscribed | SWS has a signed search filter; seller inventory format documents signedtext. SWS long output includes seller description. | Treat the filter and description as seller/catalog claims, not authenticated signatures. |
| Dust jacket | SWS supports a dustjacket filter and its long output can mark a seller-listed jacket as present. The seller inventory format has jacketcondition values. | Do not infer jacket grade from presence, or assume jacketcondition is a structured SWS response field. |
Keep each seller offer and its copy quantity distinct.
A listing is the unit to compare when condition or seller changes. AbeBooks’ SWS field matrix includes quantity at every output size, seller name/location/ID/rating in medium and long records, and vendor description in long records. Quantity means that seller offers multiple copies under the same Book ID; it is not the total number of copies for an ISBN.
Scroll to compare →
| Listing field | What it identifies | How to compare |
|---|---|---|
| Vendor ID and name | Seller identity; vendor ID is a unique AbeBooks seller identifier. | Keep seller identity on the offer, not as a property of the book edition. |
| Vendor location and rating | SWS can return seller city/country and a 1–5 rating based on order completion rate. | Preserve the rating definition and observation time; do not relabel it as a review score. |
| Quantity | Multiple copies available for the same Book ID. | Do not add this to other listings with the same ISBN without preserving each Book ID and seller. |
| Seller description | Copy-specific wording such as condition or collectible details supplied by the seller. | Keep the text attached to its listing; materially different copies should not be collapsed into one offer. |
Compare price only with currency and delivery destination attached.
SWS distinguishes listing price, seller-uploaded price and currency, shipping, and total book price. The currency and destination parameters change the returned context. AbeBooks documents destination-specific shipping for a defined set of countries; other destinations use the seller’s international shipping value. Keep the destination and retrieval time with each comparison rather than publishing static fees or delivery promises.
Scroll to compare →
| Price or shipping field | AbeBooks SWS behavior | Data treatment |
|---|---|---|
| Listing price and currency | The currency parameter sets the returned book and shipping currency; vendor price is the seller’s original price in its original currency in long output. | Store displayed price, original seller price and currency as separate observations when available. |
| Destination and target site | destinationcountry sets the shipping country; targetsite selects an AbeBooks domain and its default country/currency. Current SWS docs list Australia, Belgium, Canada, France, Germany, Italy, Japan, Spain, Switzerland, the USA and UK for country-specific shipping; other destinations use the seller’s International shipping value. | Record both parameters or defaults so prices from different markets are not compared as if equivalent. |
| Shipping and total | With shippingdetails=yes, SWS can include shipping details and min/max shipping days; total book price is book price plus shipping. | Keep shipping assumptions and observation time with the total. Do not present the days as a delivery guarantee. |
| Legacy extra-book shipping field | AbeBooks says this backward-compatible field returns 0.0 after its shipping update and is not meaningful. | Exclude it from shipping calculations; do not interpret zero as free additional-item shipping. |
AbeBooks Search Web Services is an affiliate API with its own access rules.
AbeBooks documents SWS as a REST-style API that returns XML. Searches can use ISBN, author, title, keyword or publisher. AbeBooks requires SWS users to join its Affiliate Program and request a Client Key; its published default rate is 4–5 queries per second, with HTTP 429 when that limit is exceeded.
Scroll to compare →
| SWS detail | AbeBooks documentation | Planning implication |
|---|---|---|
| Access | Affiliate Program membership followed by a requested Client Key. | Use the access path documented by AbeBooks; the Client Key authorizes SWS requests and the API scope is defined by AbeBooks. |
| Format and request rate | REST-style requests return XML; default limit is 4–5 queries per second and excess requests can return HTTP 429. | If using SWS directly, design for the documented response format and rate limit; recheck official docs before implementation. |
| Output size and missing fields | SWS offers micro, short, medium and long records. Unpopulated fields are omitted; Subjects was retired from SWS output in June 2024. | Treat omitted values as unknown/not supplied, not false or zero. Choose output size based on the needed seller and description fields. |
| Separate AbeBooks interfaces | SWS documentation is distinct from seller inventory FTP and the private Purchase API documented on the developer site. | Do not transfer fields, permissions or capabilities from one interface to another. |
Content reviewed 2026-09-29.