PatentsView-APIWrapper 1.0.0 #2
mustberuss
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
PatentsView-APIWrapper 1.0.0
The API Team has archived their repo that contained the original version of the PatentsView-APIWrapper. It worked with the original version of the API which was shutdown in May 2025. This PR updates and extends their code to work with the new version of the API, acknowlegded in README.md per its Creative Commons 4.0 license. The API team renamed the API but we'll continue to use the original name of the wrapper.
Issues and Discussions have been enabled in this repo in case they are needed.
Breaking changes
API key required: The new version of the API requires authentication. Request a key at https://patentsview-support.atlassian.net/servicedesk/customer/portals and set
PATENTSVIEW_API_KEYenvironment variable.Entity name changes: Now 27 endpoints (up from 7). Endpoints are singular (e.g.,
patentnotpatents). Thenber_subcategoryendpoint was removed;cpc_subsectionis nowcpc_group.Field changes:
patent_numberis nowpatent_id. Raw inventor name fields (rawinventor_first_name,rawinventor_last_name) were removed. Some fields are now nested and require full qualification in queries (e.g.,cpc_current.cpc_group_id).See the API team's Swagger UI page and Endpoint Dictionary
Features
Chaining Queries In the previous version queries could be chained (output of one query became the input of another), though the feature was not documented. See README.md and nested_query.cfg
Joining Queries In this new version, the input fie can be a csv that joins
join_output_onin the csv file toinput_typein the API's output. See README.md and joined_query.cfgThis discussion was created from the release PatentsView-APIWrapper 1.0.0.
Beta Was this translation helpful? Give feedback.
All reactions