Serial Title API

This provides interfaces to a search through serial titles (SCOPUS content).



The following chart shows the Serial Title Views.

Summary

Resource Method Description
https://api.elsevier.com/content/serial/title GET
Serial Title API: This represents a search against the serial titles (SCOPUS content).
https://api.elsevier.com/content/serial/title/issn/{issn} GET
Serial Title API: This represents a single serial title (SCOPUS content) identified by ISSN. This can return either the metadata for that title or the cover image.

Resources


https://api.elsevier.com/content/serial/title

Serial Title API: This represents a search against the serial titles (SCOPUS content).

Methods
GET simple()

request
header params
Accept xsd:string
(required)
default: application/json
options: application/json, text/xml, application/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 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
options: new
Represents the version of the resource that should be received. Note that submitting new always returns the latest response version.

query params
httpAccept xsd:string
options: application/json, text/xml, application/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.
start 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. start=5
count 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. count=10
view xsd:string
default: STANDARD
options: STANDARD, ENHANCED, CITESCORE
The following chart shows the Serial Title 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.
title xsd:string This represents a partial or complete serial title. Will match the pattern provided anywhere within the title -- no wildcard support is provided.



ex. title=medicine
issn xsd:string Represents the source identifier filter. One or more identifiers can be provided.

pub xsd:string Represents the publisher name. Will match the pattern provided anywhere within the publisher name -- no wildcard support is provided.



ex. pub=Elsevier
subj xsd:string Represents the SCOPUS subject area abbreviation associated with the content category desired. One or more abbreviations can be provided.



The following resource shows all of the available subject classifications.



AGRI- Agricultural and Biological Sciences

ARTS- Arts and Humanities

BIOC- Biochemistry, Genetics and Molecular Biology

BUSI- Business, Management and Accounting

CENG- Chemical Engineering

CHEM- Chemistry

COMP- Computer Science

DECI- Decision Sciences

DENT- Dentistry

EART- Earth and Planetary Sciences

ECON- Economics, Econometrics and Finance

ENER- Energy

ENGI- Engineering

ENVI- Environmental Science

HEAL- Health Professions

IMMU- Immunology and Microbiology

MATE- Materials Science

MATH- Mathematics

MEDI- Medicine

NEUR- Neuroscience

NURS- Nursing

PHAR- Pharmacology, Toxicology and Pharmaceutics

PHYS- Physics and Astronomy

PSYC- Psychology

SOCI- Social Sciences

VETE- Veterinary

MULT- Multidisciplinary
content xsd:string
options: tradejournal, journal, conferenceproceeding, bookseries
Specifies the type of source to be returned. One or more source types can be provided.



Available choices include:



tradejournal - Trade Publications

journal - Journals

conferenceproceeding - Conference Proceedings

bookseries - Book Series
date xsd:string Represents the date range for filtering info entries in EHANCED view, with the lowest granularity being year.



ex. date=2002-2007
oa xsd:string
options: all, full, partial, none
Filter used to specify whether the source titles returned should include Open Access types. If included in the request, this filter will limit the results based upon this Open Access status.



Available choices include:



all - Return all source titles, regardless of Open Access status.

full - Include only those source titles defined as FULL Open Access.

partial - Include only those source titles defined as PARTIAL Open Access.

none - Include no source titles defined as Open Access (FULL or PARTIAL).

responses
status:
200
representations
application/json Serial Title JSON Response: This is JSON representing the requested resource. JSON Example
status:
200
representations
text/xml Serial Title XML Response: This is XML representing the requested resource. XML Example
status:
200
representations
application/xml Serial Title XML Response: This is XML representing the requested resource. XML 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
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. Generic Error Example

https://api.elsevier.com/content/serial/title/issn/{issn}

Serial Title API: This represents a single serial title (SCOPUS content) identified by ISSN. This can return either the metadata for that title or the cover image.

Methods
GET simple()

request
header params
Accept xsd:string
(required)
default: application/json
options: application/json, text/xml, application/xml, image/gif
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 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
options: new
Represents the version of the resource that should be received. Note that submitting new always returns the latest response version.

query params
httpAccept xsd:string
options: application/json, text/xml, application/xml, image/gif
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: STANDARD
options: STANDARD, ENHANCED, CITESCORE, COVERIMAGE
The following chart shows the Serial Title 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.
date xsd:string Represents the date range for filtering info entries in EHANCED view, with the lowest granularity being year.



ex. date=2002-2007

responses
status:
200
representations
application/json Serial Title JSON Response: This is XML representing the requested resource. JSON Example
status:
200
representations
text/xml Serial Title XML Response: This is XML representing the requested resource. XML Example
status:
200
representations
application/xml Serial Title XML Response: This is XML representing the requested resource. XML Example
status:
200
representations
image/gif Serial Title Cover Image Response: This is the cover image associated with the requested resource. GIF 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
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. Generic Error Example