Subject Classifications API

This provides the ability to retrieve and search for the Subject Classifications associated with ScienceDirect or Scopus content.

Summary

Resource Method Description
https://api.elsevier.com/content/subject/scidir GET
Subject Classifications API - ScienceDirect: This represents the subject classifications associated with ScienceDirect content.
https://api.elsevier.com/content/subject/scopus GET
Subject Classifications API - Scopus: This represents the subject classifications associated with Scopus content.

Resources


https://api.elsevier.com/content/subject/scidir

Subject Classifications API - ScienceDirect: This represents the subject classifications associated with ScienceDirect content.

Methods
GET simple()

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

query params
httpAccept xsd:string
options: text/xml, application/json, application/xml
Override for HTTP header Accept, this represents the acceptable mime types for which the response can be generated.
description xsd:string Subject classifications are filtered based upon any word provided in the primary subject classification description. This is a case-insensitive match of any portion of the field.



ex. description=biological
detail xsd:string Subject classifications are filtered based upon any word provided in the detail attribute. This is a case-insensitive match of any portion of the field.



ex. detail=food
code xsd:string Subject classifications are filtered based upon any word provided in the code attribute. This is a case-insensitive match of the entire field.



ex. code=391
parentCode xsd:string Subject classifications are filtered based upon any word provided in the parentCode attribute. This is a case-insensitive match of the entire field.



ex. parentCode=7
abbrev xsd:string Subject classifications are filtered based upon any word provided in the abbrev attribute. This is a case-insensitive match of the entire field.



ex. abbrev=analysis
field xsd:string
options: code, abbrev, detail, description
This represents the specific fields that should be returned. If no fields are specified the entire subject-classification entry is returned.

Multiple fields can be specified, delimited by commas.

responses
status:
200
representations
application/json Subject Classification JSON Response: This is JSON representing the requested resource. JSON Example
status:
200
representations
text/xml Subject Classification 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:
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/subject/scopus

Subject Classifications API - Scopus: This represents the subject classifications associated with Scopus content.

Methods
GET simple()

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

query params
httpAccept xsd:string
options: text/xml, application/json, application/xml
Override for HTTP header Accept, this represents the acceptable mime types for which the response can be generated.
description xsd:string Subject classifications are filtered based upon any word provided in the primary subject classification description. This is a case-insensitive match of any portion of the field.



ex. description=biological
detail xsd:string Subject classifications are filtered based upon any word provided in the detail attribute. This is a case-insensitive match of any portion of the field.



ex. detail=food
code xsd:string Subject classifications are filtered based upon any word provided in the code attribute. This is a case-insensitive match of the entire field.



ex. code=1106
abbrev xsd:string Subject classifications are filtered based upon any word provided in the abbrev attribute. This is a case-insensitive match of the entire field.



ex. abbrev=AGRI
field xsd:string
options: code, abbrev, detail, description
This represents the specific fields that should be returned. If no fields are specified the entire subject-classification entry is returned.

Multiple fields can be specified, delimited by commas.

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