Skip Header

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

Binary interactions

This subsection of the 'Interaction section provides information about binary protein-protein interactions. The data presented in this section are a quality-filtered subset of binary interactions automatically derived from the IntAct database. It is updated on a monthly basis. Each binary interaction is displayed on a separate line.

We report the name of the interacting protein in the ‘With’ column along with the UniProtKB accession number of the interacting protein in the ‘Entry’ column. The latter may be the identifier of a specific isoform which participates in the interaction. The ‘#Exp’ column indicates the number of experiments in the IntAct database which support the interaction, while the ‘IntAct’ column contains the IntAct database accession numbers of the two interacting proteins. Specific information regarding the interaction may be present in the ‘Notes’ column.
Examples: P62258, Q8T4F7, P02829

Homotypic interactions are indicated by the presence of the qualifier ‘itself’ in the ‘With’ column.
Homotypic interactions are listed before heteromeric interactions, which are sorted alphanumerically based on their ‘identifier’.
Example: Q64279

If different isoforms of the protein described in the entry have been shown to interact with the same target protein (described in a different UniProtKB entry), then only one of the interactions, involving one of the isoforms, is chosen for display. The IntAct accession numbers of the given representative interaction link to the relevant isoforms.
Example: O43521 - interaction with BCL2L1 (Q07817-1).

In contrast, the corresponding reciprocal view lists all binary interactions between the sequences, including those involving specific protein isoforms.
Example: Q07817

The sentence ‘From a different organism’ in the ‘Notes’ column indicates that the interacting proteins are derived from different species. This may be due either to the experimental design or may reflect a pathogen-host interaction.
Example: Q8WUM4

UniProtKB ‘Binary interactions’ are automatically derived from the IntAct database, but represent only a subset of the binary interactions found in IntAct. The complete IntAct set can be accessed using the link in the ‘Cross-references’ section.
Example: P51617 (Protein-protein interaction databases)

Related document

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