link管理

链接快照平台

输入网页链接，自动生成快照
标签化管理网页链接

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 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.

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

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. 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. 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". 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". 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. 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. 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. 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. xsd:string Override for HTTP header X-ELS-APIKey, this represents a unique application developer key providing access to resource. 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. xsd:string Override for HTTP header X-ELS-ResourceVersion, this represents the version of the resource that should be received.
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.
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.
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. 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

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

Methods

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. 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. 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". 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". 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. 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. 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. 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. xsd:string Override for HTTP header X-ELS-APIKey, this represents a unique application developer key providing access to resource. 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. xsd:string Override for HTTP header X-ELS-ResourceVersion, this represents the version of the resource that should be received. 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 .
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.
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.
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
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 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. 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

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

Methods

status:

300

representations

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 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. 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. 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". 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". 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. 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. 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. 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. xsd:string Override for HTTP header X-ELS-APIKey, this represents a unique application developer key providing access to resource. 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. xsd:string Override for HTTP header X-ELS-ResourceVersion, this represents the version of the resource that should be received. 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 .
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.
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.
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
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 Author ORCID JSON Response: This is the JSON ORCID representation of the requested document. ORCID JSON Sample

status:

300

representations

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 technologies. Elsevier Developers is a registered trademark of Elsevier B.V.