Scopus is a living database with changes happning constantly. These are not just additions of new items (Articles, Books, …) as they are published or updated citation counts, but also backfills of existing sources and corrections. Corrections include changes of titles, names or abstracts, mergers of duplicate authors, affiliations or even research items. Mergers affect multiple entities: For example mergers of authors affect both the authors and the articles of the duplicate.

For these reasons update your cached files regularly. Implement cross-checks to verify that an abstract is also listed as publication in the author profile.

Corrections in the Scopus database can be reported here.

Error messages

Since scopus 0.2.0, an exception is raised when the download status is not ok. This is to prevent faulty information (i.e. the error status and message) being saved as cached file.

The Scopus API returns a number of errors, upon which the current scopus run interrupts and prints the error to the screen.

Here are common exception classes, status lines and possible causes:

requests.exceptions.TooManyRedirects: Exceeded 30 redirects.
The entity you are looking for was not properly merged with another one entity in the sense that it is not forwarding. Happens rarely when Scopus Author profiles are merged. May also occur less often with Abstract EIDs and Affiliation IDs.
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url
Usually an invalid search query, such as a missing parenthesis. Verify that your query works in Advanced Search.
requests.exceptions.HTTPError: 401 Client Error: Unauthorized for url
Either the provided key is not correct, in which case you should change it in ~/.scopus/, or you are outside the network that provides you access to the Scopus database (e.g. your university network). Remember that you need both to access Scopus.
requests.exceptions.HTTPError: 404 Client Error: Not Found for url
The entity you are looking for does not exist. Check that your identifier is still pointing to the item you are looking for.
requests.exceptions.HTTPError: 421 Quota Exceeded
Your provided API key’s weekly allowance of 5000 requests (for standard views) is depleted. Wait a week or change the key in ~/.scopus/
requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url
Formally, the server does not respond, for various reasons. A common reason in searches is that you use a fieldname that does not exist. Verify that your query works in Advanced Search.


Scopus knows two types of affiliations: Org profiles and Non-Org profiles.

Org profiles are those entities, that perform or sponsor research, such as a university, research institute, or government organization, which leads to the origination of documents by its members. Affiliations that are org profiles (OrgID) according to Scopus start with a 6 (6XXXXXXX). Scopus strives to have precise information about the institution, such as type and address.

Non-Org profiles correspond to automatically clustered profiles. In theory, Non-Org profiles should correspond to research networks and virtual institutes, as they neither have a type nor an address. Affiliations that are Non-Org profiles start with a 1 (1XXXXXXXX). Often these are are duplicates of Org profiles, which should be requested to be merged here.