How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
University of Warsaw

University of Warsaw Patent API

The Patent API from University of Warsaw — 29 operation(s) for patent.

Documentation Provider Profile APIs.io OpenAPI GitHub

University of Warsaw Patent API is one of 152 APIs that University of Warsaw publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Patents. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 2 JSON Schemas.

This API exposes 43 operations across 29 paths, and defines 27 schemas. It is described by OpenAPI 3.2.0, at version 1.2.25.

Requests are made against a single base URL, https://api.jaskier.uw.edu.pl.

43 operations 29 paths 27 schemas 7 DELETE20 GET4 POST12 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.2.25
Base URL
https://danebadawcze.uw.edu.pl/api/
Authentication
API Key
Resource Areas
1

Authentication & Security 1

University of Warsaw Patent API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (Authorization).

Paths & Operations 43

Across 29 paths, the API surfaces 43 operations — 7 DELETE, 20 GET, 4 POST, 12 PUT. Each is listed below with its method, path, parameters, and response codes.

Patent 43
GET
/api/v1/Patent/{cfPatId}
Czytanie patentu z podanym id
getPatentById 1 param → 200
PUT
/api/v1/Patent/{cfPatId}
Aktualizacja patentu
updatePatent 1 param body → 200
GET
/api/v1/Patent/{cfPatId}/PatentUnit
Czytanie listy jednostek powiązanych z patentem
getPatentUnits 1 param → 200
PUT
/api/v1/Patent/{cfPatId}/PatentUnit
Dodawanie jednostki do patentu
addPatentUnit 1 param body → 200
PUT
/api/v1/Patent/{cfPatId}/PatentUnit/{patentUnitId}
Aktualizacja powiązania jednostki z patentem
updatePatentUnit 2 params body → 200
DELETE
/api/v1/Patent/{cfPatId}/PatentUnit/{patentUnitId}
Usunięcie powiązania patentu z jednostką
removePatentUnit 2 params → 200
GET
/api/v1/Patent/{cfPatId}/InstitutionalOwner
Czytanie listy współwłaścicieli instytucjonalnych patentu
getPatentInstitutionalOwners 1 param → 200
PUT
/api/v1/Patent/{cfPatId}/InstitutionalOwner
Dodawanie współwłaściciela instytucjonalnego patentu
addPatentInstitutionalOwner 1 param body → 200
PUT
/api/v1/Patent/{cfPatId}/InstitutionalOwner/{ownerId}
Aktualizacja współwłaściciela instytucjonalnego patentu
updatePatentInstitutionalOwner 2 params body → 200
DELETE
/api/v1/Patent/{cfPatId}/InstitutionalOwner/{ownerId}
Usunięcie współwłaściciela instytucjonalnego patentu
removePatentInstitutionalOwner 2 params → 200
GET
/api/v1/Patent/{cfPatId}/Financing
Czytanie listy źródeł finansowania patentu
getPatentFinancing 1 param → 200
PUT
/api/v1/Patent/{cfPatId}/Financing
Dodawanie źródła finansowania patentu
addPatentFinancing 1 param body → 200
PUT
/api/v1/Patent/{cfPatId}/Financing/{financingId}
Aktualizacja źródła finansowania patentu
updatePatentFinancing 2 params body → 200
DELETE
/api/v1/Patent/{cfPatId}/Financing/{financingId}
Usunięcie źródła finansowania patentu
removePatentFinancing 2 params → 200
GET
/api/v1/Patent/{cfPatId}/ContactPerson
Czytanie listy osób kontaktowych patentu
getPatentContactPersons 1 param → 200
PUT
/api/v1/Patent/{cfPatId}/ContactPerson
Dodawanie osób kontaktowych do patentu
addPatentContactPerson 1 param body → 200
PUT
/api/v1/Patent/{cfPatId}/ContactPerson/{contactPersonId}
Aktualizacja danych o autorze patentu
updatePatentContactPerson 2 params body → 200
DELETE
/api/v1/Patent/{cfPatId}/ContactPerson/{contactPersonId}
Usunięcie osoby kontaktowej patentu
removePatentContactPerson 2 params → 200
GET
/api/v1/Patent/{cfPatId}/Author
Czytanie listy autorów patentu
getPatentAuthors 1 param → 200
PUT
/api/v1/Patent/{cfPatId}/Author
Dodawanie autorów patentu
addPatentAuthor 1 param body → 200
PUT
/api/v1/Patent/{cfPatId}/Author/{authorId}
Aktualizacja danych o autorze patentu
updatePatentAuthor 2 params body → 200
DELETE
/api/v1/Patent/{cfPatId}/Author/{authorId}
Usunięcie autora patentu
removePatentAuthor 2 params → 200
GET
/api/v1/Patent/{cfPatId}/Abstract
Lista abstraktów dla danego patentu
getPatentAbstracts 1 param → 200
PUT
/api/v1/Patent/{cfPatId}/Abstract
Dodawanie abstraktu do patentu
addPatentAbstract 1 param body → 200
GET
/api/v1/Patent
Listowanie danych o patentach
queryForPatent → 200
POST
/api/v1/Patent
Dodawanie patentu
addPatent body → 200
POST
/api/v1/Patent/{patentId}/Copy
Utworzenie kopii patentu z podanym id
copyPatentById 1 param body → 200
POST
/api/v1/Patent/{cfPatId}/Notes
Aktualizacja notatek do patentu
upsertPatentNotes 1 param body → 200
POST
/api/v1/Patent/{cfPatId}/Abstract/{cfAbstrId}
Aktualizacja abstraktu dla patentu
updatePatentAbstract 2 params body → 200
DELETE
/api/v1/Patent/{cfPatId}/Abstract/{cfAbstrId}
Usunięcie abstraktu dla patentu
removePatentAbstract 2 params → 200
GET
/api/v1/Patent/{cfPatId}/History
Czytanie historii zmian patentu
getPatentHistory 1 param → 200
GET
/api/v1/Patent/my
Listowanie patentów zalogowanego użytkownika
queryForMyPatent → 200
GET
/api/v1/Patent/Units
Listowanie jednostek
getUnitsForPatent → 200
GET
/api/v1/Patent/SearchProfile
Wyszukiwanie profilu (np. w celu wpisania jako autora)
searchProfileForPatent 5 params → 200
GET
/api/v1/Patent/SearchProfile('{profileId}')
Czytanie informacji o profilu
getSearchProfileForPatent 1 param → 200
GET
/api/v1/Patent/SearchPerson
Wyszukiwanie osoby (np. w celu wpisania jako osoby kontaktowej)
searchPersonForPatent 5 params → 200
GET
/api/v1/Patent/SearchPerson('{personId}')
Czytanie informacji o osobie
getSearchPersonForPatent 1 param → 200
GET
/api/v1/Patent/ProtectionTypes
Zwraca listę wszystkich rodzajów ochrony (lookup)
getPatentProtectionTypes → 200
GET
/api/v1/Patent/ProtectionSubjects
Zwraca listę wszystkich przedmiotów ochrony (lookup)
getPatentProtectionSubjects → 200
GET
/api/v1/Patent/PatentInternationalOrganizations
Zwraca listę organizacji międzynarodowych powiązanych z obsługą patentów
getPatentInternationalOrganizations → 200
GET
/api/v1/Patent/FinancingSources
Czytanie listy wszystkich źródeł finansowania (lookup)
getPatentFinancingSources → 200
GET
/api/v1/Patent/BusinessEntities
Listowanie podmiotów
getBusinessEntitiesForPatent → 200
DELETE
/api/v1/Patent/{cfPatId}/Remove
Usunięcie patentu
removePatent 2 params → 200

Schemas 27

The contract defines 27 schemas that model the data the API accepts and returns. The most detailed are PatentResponse (39 properties), PatentRequest (35 properties), QueryProfileItemResponse (33 properties), QueryPatentsItemResponse (32 properties). Each schema is shown below with its type and property counts.

QueryProfileItemResponse
object
33 properties
HistoryResponse
object
11 properties
PatentUnitRequest
object
3 properties 1 required
ProtectionSubjectResponse
object
3 properties
PatentFinancingRequest
object
2 properties 2 required
AdditionalInfoRequest
object
1 property
PatentFinancingResponse
object
Współwłaściciel instytucjonalny patentu
4 properties
PatentInstitutionalOwnerResponse
object
Współwłaściciel instytucjonalny patentu
5 properties
AbstractResponse
object
9 properties
PatentInstitutionalOwnerRequest
object
3 properties 2 required
PatentAuthorRequest
object
6 properties 2 required
BusinessEntityResponse
object
Podmiot
5 properties
UnitViewResponse
object
Jednostki organizacyjne
8 properties
PatentRequest
object
35 properties 2 required
ProtectionTypeResponse
object
3 properties
OdataResponseQueryProfileItemResponse
object
2 properties
OdataResponsePersonViewResponse
object
2 properties
CopyPatentRequest
object
3 properties 3 required
AbstractRequest
object
7 properties 1 required
PatentUnitResponse
object
5 properties
PatentContactPersonRequest
object
Osoba kontaktowa patentu
5 properties 1 required
PatentContactPersonResponse
object
Osoba kontaktowa patentu
7 properties
PatentResponse
object
Szczegółowe informacje o patencie
39 properties
PersonViewResponse
object
10 properties
ProfileResponse
object
22 properties
PatentAuthorResponse
object
Autor patentu
13 properties
QueryPatentsItemResponse
object
Podstawowe informacje o patencie
32 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

university-of-warsaw-patent-api-openapi.yml Raw ↑

Other APIs University of Warsaw publishes across the network.

Dane Badawcze UW Research Data Repository REST API
AE Profile APIs.io
Dane Badawcze UW OAI-PMH Endpoint
AE Profile APIs.io
University of Warsaw Apiref API
AE Profile APIs.io
University of Warsaw Apisrv API
AE Profile APIs.io
University of Warsaw Calendar API
AE Profile APIs.io
University of Warsaw Courses API
AE Profile APIs.io
University of Warsaw Fac API
AE Profile APIs.io
ReIn UW Institutional Repository REST API
AE Profile APIs.io
ReIn UW OAI-PMH Endpoint
AE Profile APIs.io
University of Warsaw SAML Identity Provider (eduGAIN / PIONIER.Id)
AE Profile APIs.io
DataCite DOI Registration (REPOD / REPOD.DBUW)
AE Profile APIs.io
Crossref Membership (member 4211)
AE Profile APIs.io
#Patents
← Back to U APIs
API Details
ID
university-of-warsaw:university-of-warsaw-patent-api
Base URL
https://danebadawcze.uw.edu.pl/api/
Docs
https://danebadawcze.uw.edu.pl/
Provider
University of Warsaw
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=university-of-warsaw-patent-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/university-of-warsaw-patent-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of University of Warsaw Patent API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.