Skip Header

You are using a version of browser that may not display all the features of this website. Please consider upgrading your browser.

Programmatic access - Retrieving individual entries

Last modified February 25, 2020

The web address for an entry consists of a data set name (e.g. uniprot, uniref, uniparc, taxonomy, ...) and the entry's unique identifier, e.g.:

By default, a web page is returned. Depending on the data set, other formats may also be available (click on "Formats" on the entry's web page). Here are some examples:

Note that UniRef identifiers cannot be guaranteed to be stable, since the sequence clusters are recomputed at every release, and the representative protein may change. See also: How to link to UniProt entries.

For the RDF/XML format there is an option to include data from referenced data sets directly in the returned data: 

The following status codes may be returned:

200The request was processed successfully.
400Bad request. There is a problem with your input.
404Not found. The resource you requested doesn't exist.
410Gone. The resource you requested was removed.
500Internal server error. Most likely a temporary problem, but if the problem persists please contact us.
503Service not available. The server is being updated, try again later.

Resolving RDF identifiers

A request for an address such as

will be resolved, where possible, by redirection to the corresponding resource (see previous section). For UniProt resources, entries are returned in RDF/XML format if the HTTP 'Accept' request header is set to 'application/rdf+xml'.

See also:
REST API - Access the UniProt website programmatically - batch retrieval, ID mapping, queries, downloads, etc

UniProt is an ELIXIR core data resource
Main funding by: National Institutes of Health

We'd like to inform you that we have updated our Privacy Notice to comply with Europe’s new General Data Protection Regulation (GDPR) that applies since 25 May 2018.

Do not show this banner again