Google Patents Details by Number: status, dates, CPC, citations
Pricing
from $3.25 / 1,000 patent delivereds
Google Patents Details by Number: status, dates, CPC, citations
One structured record per patent publication number from Google Patents, up to 200 per run: title, abstract, assignee, country, priority, filing and publication dates, legal status and expiry, claim count, CPC codes and citation counts. No inventor names. Pay per delivered patent.
Pricing
from $3.25 / 1,000 patent delivereds
Rating
0.0
(0)
Developer
Steadydata Team
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
One structured record per patent publication number from Google Patents, up to 200 per run: title, abstract, assignee, country, priority, filing and publication dates, legal status and expiry, claim count, CPC codes and citation counts. No inventor names. Pay per delivered patent.
Why this scraper
- Only delivered results are charged. Inputs that fail come back as clear error records at no cost.
- Measured on real documents from three offices (US, EP, WO, 15 September 2026): title, assignee, dates, legal status, claim count, CPC codes and citation counts all read server-side, without a browser. The claim markup differs per office and both forms are handled and tested.
- No inventor names. Patents are public records, but inventors are people; this actor delivers the assignee (a company) and leaves the persons out. That keeps the data usable in any jurisdiction without a privacy review.
- By number only, by design. Google's robots.txt allows the document pages and forbids the search pages, so this actor reads exactly what is allowed. Bring your own numbers (from a watch list, a portfolio, a citation list) and get a clean record for each.
Who this is for
Patent analysts, IP teams and competitive-intelligence work that already has lists of publication numbers and needs them enriched fast: legal status and expiry for a portfolio review, CPC codes for landscaping, citation counts as a rough impact signal, assignee and dates for a timeline. Up to 200 numbers per run, one record each.
Who this is not for
- You want to search by keyword, assignee or CPC. Not possible on the allowed route; this actor needs the publication numbers as input.
- You need the full claims text, the description or the drawings. Only counts and
metadata are delivered; the document itself stays on Google Patents (the
urlfield). - You need inventor names. Deliberately not delivered.
Input fields
| Field | Type | Required or default | What it does |
|---|---|---|---|
patents | list of text | required | One per row, up to 200, as on Google Patents: US10000000B2, EP3000000B1, WO2020000001A1. A full patents.google.com URL is accepted too. |
language | text | en | Two-letter language for title and abstract, when Google has it. |
Input example
{"patents": ["US10000000B2","EP3000000B1","WO2020000001A1"],"language": "en"}
Output example
| Field | Type | What it holds | Example |
|---|---|---|---|
publicationNumber | text | The patent's publication number, the key by which it is cited everywhere. | EP3000000B1 |
title | text | The title of the patent. | System and method for detecting shaping |
abstract | text | The abstract, the one paragraph that says what the invention does. | A frequency modulated (coherent) laser detection and rang... |
assignee | text | The party the patent was granted to at publication. | Trumpf Werkzeugmaschinen SE and Co KG |
assigneeCurrent | text | The party that holds it now; different from assignee after a sale or a transfer. | Trumpf Werkzeugmaschinen SE and Co KG |
countryCode | text | The patent office that published it, as a two-letter code. | EP |
priorityDate | text | The date the priority runs from, which decides who was first. | 2013-06-24 |
filingDate | text | The date the application was filed. | 2014-06-12 |
publicationDate | text | The date this document was published. | 2017-05-17 |
legalStatus | text | Whether the patent is active, lapsed, withdrawn or expired. | Active |
expirationDate | text | The date protection ends, as far as it can be worked out. | 2036-05-13 |
claimCount | number | How many claims the patent has; a rough measure of how broad it is. | 16 |
cpcCodes | list | The CPC classification codes, the technical pigeonholes the offices file it under. | ["G05B19/00", "G05B19/02"] |
citationsBackward | number | How many earlier patents this one cites. | 0 |
citationsForward | number | How many later patents cite this one; the usual measure of how important it turned out to be. | 0 |
url | text | The patent's page on Google Patents. | https://patents.google.com/patent/EP3000000B1/en |
{"publicationNumber": "US10000000B2","title": "Coherent LADAR using intra-pixel quadrature detection","abstract": "A frequency modulated (coherent) laser detection and ranging system includes a read-out integrated circuit formed with a two-dimensional arr...","assignee": "Raytheon Co","assigneeCurrent": "Raytheon Co","countryCode": "US","priorityDate": "2015-03-10","filingDate": "2015-03-10","publicationDate": "2018-06-19","legalStatus": "Active","expirationDate": "2036-05-13","claimCount": 20,"cpcCodes": ["G01S7/00","G01S7/48","G01S7/483","G01S7/486","..."],"citationsBackward": 5,"citationsForward": 14,"url": "https://patents.google.com/patent/US10000000B2/en","status": "ok"}
Error codes: INVALID_NUMBER (not a publication number), NOT_FOUND (Google Patents has no
such document), BLOCKED (consent or bot wall after retries), FETCH_FAILED. None is charged.
Related actors from steadydata
- website-tech-stack: what the assignee's website runs on
- google-trends-batch: whether interest in the technology is rising
- google-news: news coverage of the assignee or the technology
Pricing
Pay per event: one patent-delivered event per delivered result. No charge for inputs
that fail, no separate platform-usage surcharge.
Free Apify plan: this actor delivers up to 25 rows per run for accounts on the Apify free plan, and then stops with a message. That limit is set by us, not by Apify. It exists so the actor keeps paying for itself for the people who do pay. Any paid Apify plan runs it at full size, billed per delivered row, with failed rows never charged.
Reviews: if this actor saves you time, a short review on this page is the one thing that helps most. Ratings are what other buyers look at first, and we have no other way to ask.
FAQ
Which numbers work? Any publication number Google Patents knows: US10000000B2, EP3000000B1, WO2020000001A1, CN, JP, KR and others. A full patents.google.com URL is fine too. Numbers are normalised (spaces, dashes and lowercase are accepted).
What does legalStatus contain? Google's own status label: Active, Ceased, Expired,
Pending, Withdrawn. expirationDate is present when Google shows one (granted patents).
Why is claimCount sometimes lower than I expected? It counts the numbered claims on
the page. Applications published without claims on Google Patents get 0.
What happens with a number that does not exist? A NOT_FOUND error record and no
charge. Blocked requests are retried on a fresh exit before they are reported.
Is any personal data collected? No. Inventor names are on the page and are deliberately left out; the assignee is an organisation.
Is personal data collected? No. Inventor names are deliberately left out; only the assignee (an organisation) is delivered.
What happens when the source changes? Sources change from time to time; that is the nature of this work. The actor is monitored daily and fixed fast, and while it is broken you are not charged, because only delivered results cost anything.
Is this an alternative to the PatentsView API? For patent details by number, yes. The PatentsView search API went offline in March 2026 when PatentsView moved to the USPTO Open Data Portal. This actor reads the public Google Patents page for each number, so it also covers EP, WO and other offices, not only US patents. It is not a bulk download of the whole patent corpus.
Can I call it from my own code, like an API? Yes. Every run is available through the Apify API: start it with one HTTP request, then read the results as JSON, CSV or Excel from the dataset endpoint, or use the official Python and JavaScript clients. The input is the same JSON as in the input example above, so a scheduled script, a Make or Zapier step or an AI agent can call it without any changes.