Skip to main content

Elsevier Developer Portal

Author Retrieval API

This represents retrieval of a Scopus Author Profile. The document can contain links to Scopus Search and Affiliation Profiles. The author profiles are indexed and can be searched using Author Search API.



Schemas for the 'author-profile' element of the full author profile can be found at https://schema.elsevier.com/dtds/document/profile/.



The following chart shows the Author Retrieval Views.

Summary

Resource Method Description
https://api.elsevier.com/content/author GET
 Author Retrieval API: This represents retrieval of one or more SCOPUS Author Profiles by a unique Electronic or Author ID. Note that certain views and mime types are not supported under this resource, although specifying a single document identifier produces similar behavior to a single Author Profile resource request.
https://api.elsevier.com/content/author/author_id/{author_id} GET
 Author Retrieval API: This represents retrieval of a SCOPUS Author Profile by the unique Author ID.
https://api.elsevier.com/content/author/eid/{eid} GET
 Author Retrieval API: This represents retrieval of a SCOPUS Author Profile by EID (Electronic Identifier).
https://api.elsevier.com/content/author/orcid/{orcid} GET
 Author Retrieval API: This represents retrieval of a SCOPUS Author Profile by ORCID.

Resources


https://api.elsevier.com/content/author

Author Retrieval API: This represents retrieval of one or more SCOPUS Author Profiles by a unique Electronic or Author ID. Note that certain views and mime types are not supported under this resource, although specifying a single document identifier produces similar behavior to a single Author Profile resource request.

Methods
GET simple()

request
header params
Accept xsd:string
(required)
default: text/xml
options: text/xml, application/xml, application/json, application/rdf+xml		 This represents the acceptable mime types in which the response can be generated. This can also be submitted as the query string parameter "httpAccept". This returns the response in JSON, ATOM, or XML mark-up.
Authorization xsd:string This header field contains the OAuth bearer access token in which the format of the field is "Bearer <token>" (where the token represents the end-user session key). The presence of a bearer token implies the request will be executed against user-based entitlements. The Authorization field overrides X-ELS-Authtoken.
X-ELS-APIKey xsd:string
(required) 		This represents a unique application developer key providing access to API resources. This key can also be submitted as the query string parameter "apiKey"
X-ELS-Authtoken xsd:string This represents a end-user session. If provided, this token is used to validate the credentials needed to access content in this resource. This token can also be submitted through the HTTP header "Authorization" or the query string parameter "access_token".
X-ELS-Insttoken xsd:string This represents a institution token. If provided, this key (in combination with its associated APIKey) is used to establish the credentials needed to access content in this resource. This token can also be provided through the query string parameter "insttoken".
X-ELS-ReqId xsd:string This is a client-defined request identifier, which will be logged in all trace messages of the service. This identifier can be used to track a specific transaction in the service's message logs. It will also be returned as an HTTP header in the corresponding response. Note that this should be a unique identifier for the client, and used to track a single transaction.
X-ELS-ResourceVersion xsd:string Represents the version of the resource that should be received.

query params
httpAccept xsd:string
options: text/xml, application/xml, application/json, application/rdf+xml		 Override for HTTP header Accept, this represents the acceptable mime types for which the response can be generated.
access_token xsd:string Override for HTTP header Authorization, this contains the OAuth bearer access token, where the format of the field is "<token>" (where the token represents the end-user session key). The presence of a bearer token implies the request will be executed against user-based entitlements.
insttoken xsd:string Override for HTTP header X-ELS-Insttoken, this represents a institution token. If provided, this key (in combination with its associated APIKey) is used to establish the credentials needed to access content in this resource.
apiKey xsd:string Override for HTTP header X-ELS-APIKey, this represents a unique application developer key providing access to resource.
reqId xsd:string Override for HTTP header X-ELS-ReqId, this is a client-defined request identifier, which will be logged in all trace messages of the service. This identifier can be used to track a specific transaction in the service's message logs. Note that this should be a unique identifier for the client, and used to track a single transaction.
ver xsd:string Override for HTTP header X-ELS-ResourceVersion, this represents the version of the resource that should be received.
eid xsd:string

This represents the unique Electronic ID corresponding to a Scopus Author Profile. Multiple identifiers can be specified, delimited by commas.



Note that either the eid or the author_id should be specified, but not both.
author_id xsd:string

This represents the unique identifier corresponding to a Scopus Author Profile. Multiple identifiers can be specified, delimited by commas.



Note that either the eid or the author_id should be specified, but not both.
view xsd:string
default: LIGHT
options: LIGHT, STANDARD, ENHANCED, METRICS, ENTITLED

This alias represents the list of elements that will be returned in the response.



The following chart shows the Author Retrieval Views.

field xsd:string

This alias represents the name of specific fields that should be returned. The list of fields include all of the fields returned in the response payload (see view).

Multiple fields can be specified, delimited by commas.

responses
status:
200
representations
text/xml Author XML Response: This is XML representing the requested document. XML Sample
status:
200
representations
application/xml Author XML Response: This is XML representing the requested document. XML Sample
status:
200
representations
application/json Author JSON Response: This is JSON representing the requested document. JSON Sample
status:
200
representations
application/rdf+xml Author RDF Response: This is RDF representing the requested document. RDF Sample
status:
400
representations
text/xml Invalid Request: This is an error that occurs when invalid information is submitted. Invalid Request Example
status:
401
representations
text/xml Authentication Error: This is an error that occurs when a user cannot be authenticated due to missing/invalid credentials (authtoken or APIKey). Authentication Error Example
status:
403
representations
text/xml Authorization/Entitlements Error: This is an error that occurs when a user cannot be authenticated or entitlements cannot be validated. Authorization Error Example
status:
404
representations
text/xml Resource Not Found Error: This is an error that occurs when the requested resource cannot be found. Resource Not Found Example
status:
405
representations
text/xml Invalid HTTP Method: This is an error that occurs when the requested HTTP Method is invalid. Invalid Method Example
status:
406
representations
text/xml Invalid Mime Type: This is an error that occurs when the requested mime type is invalid. Invalid Mime Type Example
status:
429
representations
text/xml Quota Exceeded: This is an error that occurs when a requester has exceeded the quota limits associated with their API Key. Quota Exceeded Example
status:
500
representations
text/xml Generic Error: This is a general purpose error condition, typically due to back-end processing errors. Generic Error Example

https://api.elsevier.com/content/author/author_id/{author_id}

Author Retrieval API: This represents retrieval of a SCOPUS Author Profile by the unique Author ID.

Methods
GET simple()

request
header params
Accept xsd:string
(required)
default: text/xml
options: text/xml, application/xml, application/json, application/x-orcid+xml, application/x-orcid+json, application/rdf+xml		 This represents the acceptable mime types in which the response can be generated. This can also be submitted as the query string parameter "httpAccept". This returns the response in JSON, ATOM, or XML mark-up.
Authorization xsd:string This header field contains the OAuth bearer access token in which the format of the field is "Bearer <token>" (where the token represents the end-user session key). The presence of a bearer token implies the request will be executed against user-based entitlements. The Authorization field overrides X-ELS-Authtoken.
X-ELS-APIKey xsd:string
(required) 		This represents a unique application developer key providing access to API resources. This key can also be submitted as the query string parameter "apiKey"
X-ELS-Authtoken xsd:string This represents a end-user session. If provided, this token is used to validate the credentials needed to access content in this resource. This token can also be submitted through the HTTP header "Authorization" or the query string parameter "access_token".
X-ELS-Insttoken xsd:string This represents a institution token. If provided, this key (in combination with its associated APIKey) is used to establish the credentials needed to access content in this resource. This token can also be provided through the query string parameter "insttoken".
X-ELS-ReqId xsd:string This is a client-defined request identifier, which will be logged in all trace messages of the service. This identifier can be used to track a specific transaction in the service's message logs. It will also be returned as an HTTP header in the corresponding response. Note that this should be a unique identifier for the client, and used to track a single transaction.
X-ELS-ResourceVersion xsd:string Represents the version of the resource that should be received.

query params
httpAccept xsd:string
options: text/xml, application/xml, application/json, application/x-orcid+xml, application/x-orcid+json, application/rdf+xml		 Override for HTTP header Accept, this represents the acceptable mime types for which the response can be generated.
access_token xsd:string Override for HTTP header Authorization, this contains the OAuth bearer access token, where the format of the field is "<token>" (where the token represents the end-user session key). The presence of a bearer token implies the request will be executed against user-based entitlements.
insttoken xsd:string Override for HTTP header X-ELS-Insttoken, this represents a institution token. If provided, this key (in combination with its associated APIKey) is used to establish the credentials needed to access content in this resource.
apiKey xsd:string Override for HTTP header X-ELS-APIKey, this represents a unique application developer key providing access to resource.
reqId xsd:string Override for HTTP header X-ELS-ReqId, this is a client-defined request identifier, which will be logged in all trace messages of the service. This identifier can be used to track a specific transaction in the service's message logs. Note that this should be a unique identifier for the client, and used to track a single transaction.
ver xsd:string Override for HTTP header X-ELS-ResourceVersion, this represents the version of the resource that should be received.
view xsd:string
default: LIGHT
options: LIGHT, STANDARD, ENHANCED, METRICS, DOCUMENTS, ENTITLED, ORCID, ORCID_BIO, ORCID_WORKS

This alias represents the list of elements that will be returned in the response.



The following chart shows the Author Retrieval Views.
field xsd:string

This alias represents the name of specific fields that should be returned. The list of fields include all of the fields returned in the response payload (see view).

Multiple fields can be specified, delimited by commas.
alias xsd:string
default: true
options: true, false

This parameter controls the default behavior of returning a superseded author profile. Submitting this value as false will override the default behavior and return the author profile information, even if it has been superseded.
startref xsd:string

Numeric value representing the results offset (i.e. starting position for the search results). The maximum for this value is a system-level default (varies with search cluster) minus the number of results requested. If not specified the offset will be set to zero (i.e. first search result)



ex. startref=5
refcount xsd:string

Numeric value representing the maximum number of results to be returned for the search. If not provided this will be set to a system default based on service level.

In addition the number cannot exceed the maximum system default - if it does an error will be returned.



ex. refcount=10

responses
status:
200
representations
text/xml Author XML Response: This is XML representing the requested document. XML Sample
status:
200
representations
application/xml Author XML Response: This is XML representing the requested document. XML Sample
status:
200
representations
application/json Author JSON Response: This is JSON representing the requested document. JSON Sample
status:
200
representations
application/rdf+xml Author RDF Response: This is RDF representing the requested document. RDF Sample
status:
200
representations
application/x-orcid+xml Author ORCID XML Response: This is XML ORCID representation of the requested document. ORCID XML Sample
status:
200
representations
application/x-orcid+json Author ORCID JSON Response: This is the JSON ORCID representation of the requested document. ORCID JSON Sample
status:
300
representations
text/xml Multiple Author Replacement: This represents the scenario when a single author profile has been superseded by multiple author profiles.
status:
301
representations
text/xml Single Author Replacement: This is redirection to a single author location when an author profile has been superseded.
status:
400
representations
text/xml Invalid Request: This is an error that occurs when invalid information is submitted. Invalid Request Example
status:
401
representations
text/xml Authentication Error: This is an error that occurs when a user cannot be authenticated due to missing/invalid credentials (authtoken or APIKey). Authentication Error Example
status:
403
representations
text/xml Authorization/Entitlements Error: This is an error that occurs when a user cannot be authenticated or entitlements cannot be validated. Authorization Error Example
status:
404
representations
text/xml Resource Not Found Error: This is an error that occurs when the requested resource cannot be found. Resource Not Found Example
status:
405
representations
text/xml Invalid HTTP Method: This is an error that occurs when the requested HTTP Method is invalid. Invalid Method Example
status:
406
representations
text/xml Invalid Mime Type: This is an error that occurs when the requested mime type is invalid. Invalid Mime Type Example
status:
429
representations
text/xml Quota Exceeded: This is an error that occurs when a requester has exceeded the quota limits associated with their API Key. Quota Exceeded Example
status:
500
representations
text/xml Generic Error: This is a general purpose error condition, typically due to back-end processing errors. Generic Error Example

https://api.elsevier.com/content/author/eid/{eid}

Author Retrieval API: This represents retrieval of a SCOPUS Author Profile by EID (Electronic Identifier).

Methods
GET simple()

request
header params
Accept xsd:string
(required)
default: text/xml
options: text/xml, application/xml, application/json, application/x-orcid+xml, application/x-orcid+json, application/rdf+xml		 This represents the acceptable mime types in which the response can be generated. This can also be submitted as the query string parameter "httpAccept". This returns the response in JSON, ATOM, or XML mark-up.
Authorization xsd:string This header field contains the OAuth bearer access token in which the format of the field is "Bearer <token>" (where the token represents the end-user session key). The presence of a bearer token implies the request will be executed against user-based entitlements. The Authorization field overrides X-ELS-Authtoken.
X-ELS-APIKey xsd:string
(required) 		This represents a unique application developer key providing access to API resources. This key can also be submitted as the query string parameter "apiKey"
X-ELS-Authtoken xsd:string This represents a end-user session. If provided, this token is used to validate the credentials needed to access content in this resource. This token can also be submitted through the HTTP header "Authorization" or the query string parameter "access_token".
X-ELS-Insttoken xsd:string This represents a institution token. If provided, this key (in combination with its associated APIKey) is used to establish the credentials needed to access content in this resource. This token can also be provided through the query string parameter "insttoken".
X-ELS-ReqId xsd:string This is a client-defined request identifier, which will be logged in all trace messages of the service. This identifier can be used to track a specific transaction in the service's message logs. It will also be returned as an HTTP header in the corresponding response. Note that this should be a unique identifier for the client, and used to track a single transaction.
X-ELS-ResourceVersion xsd:string Represents the version of the resource that should be received.

query params
httpAccept xsd:string
options: text/xml, application/xml, application/json, application/x-orcid+xml, application/x-orcid+json, application/rdf+xml		 Override for HTTP header Accept, this represents the acceptable mime types for which the response can be generated.
access_token xsd:string Override for HTTP header Authorization, this contains the OAuth bearer access token, where the format of the field is "<token>" (where the token represents the end-user session key). The presence of a bearer token implies the request will be executed against user-based entitlements.
insttoken xsd:string Override for HTTP header X-ELS-Insttoken, this represents a institution token. If provided, this key (in combination with its associated APIKey) is used to establish the credentials needed to access content in this resource.
apiKey xsd:string Override for HTTP header X-ELS-APIKey, this represents a unique application developer key providing access to resource.
reqId xsd:string Override for HTTP header X-ELS-ReqId, this is a client-defined request identifier, which will be logged in all trace messages of the service. This identifier can be used to track a specific transaction in the service's message logs. Note that this should be a unique identifier for the client, and used to track a single transaction.
ver xsd:string Override for HTTP header X-ELS-ResourceVersion, this represents the version of the resource that should be received.
view xsd:string
default: LIGHT
options: LIGHT, STANDARD, ENHANCED, METRICS, DOCUMENTS, ENTITLED, ORCID, ORCID_BIO, ORCID_WORKS

This alias represents the list of elements that will be returned in the response.



The following chart shows the Author Retrieval Views.
field xsd:string

This alias represents the name of specific fields that should be returned. The list of fields include all of the fields returned in the response payload (see view).

Multiple fields can be specified, delimited by commas.
alias xsd:string
default: true
options: true, false

This parameter controls the default behavior of returning a superseded author profile. Submitting this value as false will override the default behavior and return the author profile information, even if it has been superseded.
startref xsd:string

Numeric value representing the results offset (i.e. starting position for the search results). The maximum for this value is a system-level default (varies with search cluster) minus the number of results requested. If not specified the offset will be set to zero (i.e. first search result)



ex. startref=5
refcount xsd:string

Numeric value representing the maximum number of results to be returned for the search. If not provided this will be set to a system default based on service level.

In addition the number cannot exceed the maximum system default - if it does an error will be returned.



ex. refcount=10

responses
status:
200
representations
text/xml Author XML Response: This is XML representing the requested document. XML Sample
status:
200
representations
application/xml Author XML Response: This is XML representing the requested document. XML Sample
status:
200
representations
application/json Author JSON Response: This is JSON representing the requested document. JSON Sample
status:
200
representations
application/rdf+xml Author RDF Response: This is RDF representing the requested document. RDF Sample
status:
200
representations
application/x-orcid+xml Author ORCID XML Response: This is XML ORCID representation of the requested document. ORCID XML Sample
status:
200
representations
application/x-orcid+json Author ORCID JSON Response: This is the JSON ORCID representation of the requested document. ORCID JSON Sample
status:
300
representations
text/xml Multiple Author Replacement: This represents the scenario when a single author profile has been superseded by multiple author profiles.
status:
301
representations
text/xml Single Author Replacement: This is redirection to a single author location when an author profile has been superseded.
status:
400
representations
text/xml Invalid Request: This is an error that occurs when invalid information is submitted. Invalid Request Example
status:
401
representations
text/xml Authentication Error: This is an error that occurs when a user cannot be authenticated due to missing/invalid credentials (authtoken or APIKey). Authentication Error Example
status:
403
representations
text/xml Authorization/Entitlements Error: This is an error that occurs when a user cannot be authenticated or entitlements cannot be validated. Authorization Error Example
status:
404
representations
text/xml Resource Not Found Error: This is an error that occurs when the requested resource cannot be found. Resource Not Found Example
status:
405
representations
text/xml Invalid HTTP Method: This is an error that occurs when the requested HTTP Method is invalid. Invalid Method Example
status:
406
representations
text/xml Invalid Mime Type: This is an error that occurs when the requested mime type is invalid. Invalid Mime Type Example
status:
429
representations
text/xml Quota Exceeded: This is an error that occurs when a requester has exceeded the quota limits associated with their API Key. Quota Exceeded Example
status:
500
representations
text/xml Generic Error: This is a general purpose error condition, typically due to back-end processing errors. Generic Error Example

https://api.elsevier.com/content/author/orcid/{orcid}

Author Retrieval API: This represents retrieval of a SCOPUS Author Profile by ORCID.

Methods
GET simple()

request
header params
Accept xsd:string
(required)
default: text/xml
options: text/xml, application/xml, application/json, application/x-orcid+xml, application/x-orcid+json, application/rdf+xml		 This represents the acceptable mime types in which the response can be generated. This can also be submitted as the query string parameter "httpAccept". This returns the response in JSON, ATOM, or XML mark-up.
Authorization xsd:string This header field contains the OAuth bearer access token in which the format of the field is "Bearer <token>" (where the token represents the end-user session key). The presence of a bearer token implies the request will be executed against user-based entitlements. The Authorization field overrides X-ELS-Authtoken.
X-ELS-APIKey xsd:string
(required) 		This represents a unique application developer key providing access to API resources. This key can also be submitted as the query string parameter "apiKey"
X-ELS-Authtoken xsd:string This represents a end-user session. If provided, this token is used to validate the credentials needed to access content in this resource. This token can also be submitted through the HTTP header "Authorization" or the query string parameter "access_token".
X-ELS-Insttoken xsd:string This represents a institution token. If provided, this key (in combination with its associated APIKey) is used to establish the credentials needed to access content in this resource. This token can also be provided through the query string parameter "insttoken".
X-ELS-ReqId xsd:string This is a client-defined request identifier, which will be logged in all trace messages of the service. This identifier can be used to track a specific transaction in the service's message logs. It will also be returned as an HTTP header in the corresponding response. Note that this should be a unique identifier for the client, and used to track a single transaction.
X-ELS-ResourceVersion xsd:string Represents the version of the resource that should be received.

query params
httpAccept xsd:string
options: text/xml, application/xml, application/json, application/x-orcid+xml, application/x-orcid+json, application/rdf+xml		 Override for HTTP header Accept, this represents the acceptable mime types for which the response can be generated.
access_token xsd:string Override for HTTP header Authorization, this contains the OAuth bearer access token, where the format of the field is "<token>" (where the token represents the end-user session key). The presence of a bearer token implies the request will be executed against user-based entitlements.
insttoken xsd:string Override for HTTP header X-ELS-Insttoken, this represents a institution token. If provided, this key (in combination with its associated APIKey) is used to establish the credentials needed to access content in this resource.
apiKey xsd:string Override for HTTP header X-ELS-APIKey, this represents a unique application developer key providing access to resource.
reqId xsd:string Override for HTTP header X-ELS-ReqId, this is a client-defined request identifier, which will be logged in all trace messages of the service. This identifier can be used to track a specific transaction in the service's message logs. Note that this should be a unique identifier for the client, and used to track a single transaction.
ver xsd:string Override for HTTP header X-ELS-ResourceVersion, this represents the version of the resource that should be received.
view xsd:string
default: LIGHT
options: LIGHT, STANDARD, ENHANCED, METRICS, DOCUMENTS, ENTITLED, ORCID, ORCID_BIO, ORCID_WORKS

This alias represents the list of elements that will be returned in the response.



The following chart shows the Author Retrieval Views.
field xsd:string

This alias represents the name of specific fields that should be returned. The list of fields include all of the fields returned in the response payload (see view).

Multiple fields can be specified, delimited by commas.
alias xsd:string
default: true
options: true, false

This parameter controls the default behavior of returning a superseded author profile. Submitting this value as false will override the default behavior and return the author profile information, even if it has been superseded.
startref xsd:string

Numeric value representing the results offset (i.e. starting position for the search results). The maximum for this value is a system-level default (varies with search cluster) minus the number of results requested. If not specified the offset will be set to zero (i.e. first search result)



ex. startref=5
refcount xsd:string

Numeric value representing the maximum number of results to be returned for the search. If not provided this will be set to a system default based on service level.

In addition the number cannot exceed the maximum system default - if it does an error will be returned.



ex. refcount=10

responses
status:
200
representations
text/xml Author XML Response: This is XML representing the requested document. XML Sample
status:
200
representations
application/xml Author XML Response: This is XML representing the requested document. XML Sample
status:
200
representations
application/json Author JSON Response: This is JSON representing the requested document. JSON Sample
status:
200
representations
application/rdf+xml Author RDF Response: This is RDF representing the requested document. RDF Sample
status:
200
representations
application/x-orcid+xml Author ORCID XML Response: This is XML ORCID representation of the requested document. ORCID XML Sample
status:
200
representations
application/x-orcid+json Author ORCID JSON Response: This is the JSON ORCID representation of the requested document. ORCID JSON Sample
status:
300
representations
text/xml Multiple Author Replacement: This represents the scenario when a single author profile has been superseded by multiple author profiles.
status:
301
representations
text/xml Single Author Replacement: This is redirection to a single author location when an author profile has been superseded.
status:
400
representations
text/xml Invalid Request: This is an error that occurs when invalid information is submitted. Invalid Request Example
status:
401
representations
text/xml Authentication Error: This is an error that occurs when a user cannot be authenticated due to missing/invalid credentials (authtoken or APIKey). Authentication Error Example
status:
403
representations
text/xml Authorization/Entitlements Error: This is an error that occurs when a user cannot be authenticated or entitlements cannot be validated. Authorization Error Example
status:
404
representations
text/xml Resource Not Found Error: This is an error that occurs when the requested resource cannot be found. Resource Not Found Example
status:
405
representations
text/xml Invalid HTTP Method: This is an error that occurs when the requested HTTP Method is invalid. Invalid Method Example
status:
406
representations
text/xml Invalid Mime Type: This is an error that occurs when the requested mime type is invalid. Invalid Mime Type Example
status:
429
representations
text/xml Quota Exceeded: This is an error that occurs when a requester has exceeded the quota limits associated with their API Key. Quota Exceeded Example
status:
500
representations
text/xml Generic Error: This is a general purpose error condition, typically due to back-end processing errors. Generic Error Example