Author Feedback API
This interface provides access to the Author Feedback API.
Related Documentation: Scopus Author Feedback
Note: The related Author Feedback documentation may contain parameters not supported
through this resource. It is provided as a detailed reference for supported parameters
and for use case examples.
Summary
Resources
Search for an abstract by Scopus article eid.
Methods
request
header params
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-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.
|
query params
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.
|
responses
status:
200
representations
application/json |
Feedback Abstract JSON Response:
This is JSON representing the requested resource.
|
JSON Example |
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 (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
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
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 |
Obtain a list of documents that belong to each of the unique authors specified. Example BODY
Methods
request
header params
Accept |
xsd:string (required) default: application/json options:
application/json |
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.
|
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-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.
|
query params
httpaccept |
xsd:string options:
application/json |
Override for HTTP header Accept, this represents the acceptable mime types in which
the response can be generated.
|
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.
|
responses
status:
200
representations
application/json |
Feedback Authorship JSON Response:
This is JSON representing the requested document.
|
JSON Example |
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
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
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 |
Retrieve a list of articles by eids, author ids, or item titles. Example BODY
Methods
request
header params
Accept |
xsd:string (required) default: application/json options:
application/json |
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.
|
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-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.
|
query params
httpaccept |
xsd:string options:
application/json |
Override for HTTP header Accept, this represents the acceptable mime types in which
the response can be generated.
|
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.
|
responses
status:
200
representations
application/json |
Feedback Article JSON Response:
This is JSON representing the requested document.
|
JSON Example |
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
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
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 |
Retrieve authors based on author id or matching first/last names. Results may be filtered
by affiliation names or ids. Example BODY
Methods
request
header params
Accept |
xsd:string (required) default: application/json options:
application/json |
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.
|
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-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.
|
query params
httpaccept |
xsd:string options:
application/json |
Override for HTTP header Accept, this represents the acceptable mime types in which
the response can be generated.
|
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.
|
responses
status:
200
representations
application/json |
Feedback Author JSON Response:
This is JSON representing the requested document.
|
JSON Example |
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
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
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 |
Retrieve a list of authors that is similar in name to the specified author.
Methods
request
header params
Accept |
xsd:string (required) default: application/json options:
application/json |
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.
|
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-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.
|
query params
httpaccept |
xsd:string options:
application/json |
Override for HTTP header Accept, this represents the acceptable mime types in which
the response can be generated.
|
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.
|
responses
status:
200
representations
application/json |
Feedback Author Variant JSON Response:
This is JSON representing the requested document.
|
JSON Example |
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
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
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 |
Retrieve a list of authors and their sequence number for the specified eids. Example BODY
Methods
request
header params
Accept |
xsd:string (required) default: application/json options:
application/json |
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.
|
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-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.
|
query params
httpaccept |
xsd:string options:
application/json |
Override for HTTP header Accept, this represents the acceptable mime types in which
the response can be generated.
|
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.
|
responses
status:
200
representations
application/json |
Feedback Author Sequence JSON Response:
This is JSON representing the requested document.
|
JSON Example |
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
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
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 |
Retrieve a list of eids and sequence numbers for the specified author. Example BODY
Methods
request
header params
Accept |
xsd:string (required) default: application/json options:
application/json |
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.
|
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-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.
|
query params
httpaccept |
xsd:string options:
application/json |
Override for HTTP header Accept, this represents the acceptable mime types in which
the response can be generated.
|
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.
|
responses
status:
200
representations
application/json |
Feedback Single Author Sequence JSON Response:
This is JSON representing the requested document.
|
JSON Example |
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
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
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 |
Add articles to the specified author profile. Articles can be specified by eid as
either selected or unmatched articles. Example BODY
Methods
request
header params
Accept |
xsd:string (required) default: application/json options:
application/json |
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.
|
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-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.
|
query params
httpaccept |
xsd:string options:
application/json |
Override for HTTP header Accept, this represents the acceptable mime types in which
the response can be generated.
|
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.
|
responses
status:
200
representations
application/json |
Feedback Request Submit JSON Response:
This is JSON representing the requested document.
|
JSON Example |
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
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
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 |
Returns the target author profile based on the selected authors and articles. Example BODY
Methods
request
header params
Accept |
xsd:string (required) default: application/json options:
application/json |
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.
|
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-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.
|
query params
httpaccept |
xsd:string options:
application/json |
Override for HTTP header Accept, this represents the acceptable mime types in which
the response can be generated.
|
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.
|
responses
status:
200
representations
application/json |
Feedback Request Profile JSON Response:
This is JSON representing the requested document.
|
JSON Example |
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
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
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 |