id

xsd:long

This represents the ID of the Scopus publication that is being looked up.

Accept	xsd:string (required) default: application/json options: application/json, application/xml, text/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.

httpAccept	xsd:string options: application/json, application/xml, text/xml	Override for HTTP header Accept, this represents the acceptable mime types in 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.

200 200 200 400 401 403 405 406 429 500

Accept	xsd:string (required) default: application/json options: application/json, application/xml, text/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.

httpAccept	xsd:string options: application/json, application/xml, text/xml	Override for HTTP header Accept, this represents the acceptable mime types in 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.
metricTypes	xs:string (required) options: AcademicCorporateCollaboration, AcademicCorporateCollaborationImpact, AuthorCount, CitationCount, CitedPublications, CitingPatentCount, Collaboration, CollaborationImpact, FieldWeightedCitationImpact, FieldWeightedViewsImpact, JournalImpact, OutputsInTopCitationPercentiles, PaperPercentile, PatentCitationCount, PatentCitationsPerPublication, PatentCitedPublicationCount, PublicationsInTopJournalPercentiles, ViewsCount	This represents the types of metrics desired in the response. More than one can be specified. ex. metricTypes=Collaboration,CitationCount
publicationIds	xs:string	This represents the Scopus publication IDs for which metrics are desired in the response. More than one can be specified. ex. publicationIds=85047328215,85052976466
yearRange	xs:string default: 5yrs options: 3yrs, 3yrsAndCurrent, 3yrsAndCurrentAndFuture, 5yrs, 5yrsAndCurrent, 5yrsAndCurrentAndFuture, 10yrs	The year range for which to calculate the metric values. For instance, if the current year is 2018, 3yrsAndCurrentAndFuture would be 2015-2019.
includeSelfCitations	xs:boolean default: true	Whether or not to include self-citations in the metric calculations. Note that only certain metrics take this flag into consideration.
byYear	xs:boolean default: true	If set to true, metric values will be returned for each year in the range specified. If set to false, the metric values will be calculated for the entire year range.
includedDocs	xs:string default: AllPublicationTypes options: AllPublicationTypes, ArticlesOnly, ArticlesReviews, ArticlesReviewsConferencePapers, ArticlesReviewsConferencePapersBooksAndBookChapters, ConferencePapersOnly, ArticlesConferencePapers, BooksAndBookChapters	The document types to include in the metric calculations. Note that only certain metrics take this flag into consideration.
journalImpactType	xs:string default: CiteScore options: CiteScore, SNIP, SJR	The journal impact type to return from the metric calculations. This is only valid for the PublicationsInTopJournalPercentiles metric.
showAsFieldWeighted	xs:boolean default: false	Whether or not to display the metric calculations as field-weighted. This is only valid for the OutputsInTopCitationPercentiles metric.
indexType	xs:string default: hIndex options: hIndex, h5Index, gIndex, mIndex	The index type to return from the metric calculations. This is only valid for the HIndices metric.

200 200 200 400 401 403 405 406 429 500