Subject Area Lookup API

This represents the lookup interfaces associated with SciVal Subject Areas.

Summary

Resource	Method	Description
https://api.elsevier.com/analytics/scival/subjectArea/classificationType/{classificationType}	GET	Subject Area Lookup API: This returns all SciVal Subject Areas for a given classification.

https://api.elsevier.com/analytics/scival/subjectArea/{id}	GET	Subject Area Lookup API: This represents a lookup for a SciVal Subject Area.

https://api.elsevier.com/analytics/scival/subjectArea/search	GET	Subject Area Lookup API: This represents a boolean search for a SciVal Subject Area.

Resources

https://api.elsevier.com/analytics/scival/subjectArea/classificationType/{classificationType}

Subject Area Lookup API: This returns all SciVal Subject Areas for a given classification.

Methods

GET	getSubjectAreasByClassification()

request

template params

classificationType xs:string
default: ASJC
options: ASJC, FOR, FOS, KAKEN, QS, REF2014, THE, SDG, POL This represents the classification type of the subject areas that are being returned.

header params

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.

query params

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.

responses

status:

200

representations

application/json

Subject Area JSON Response: This is XML representing the requested document.

JSON Example

status:

200

representations

application/xml

Subject Area XML Response: This is XML representing the requested document.

XML Example

status:

200

representations

text/xml

Subject Area XML Response: This is XML representing the requested document.

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:

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

https://api.elsevier.com/analytics/scival/subjectArea/{id}

Subject Area Lookup API: This represents a lookup for a SciVal Subject Area.

Methods

GET	getSubjectArea()

request

template params

id	xsd:long	This represents the ID of the SciVal Subject Area that is being looked up.
classificationType	xs:string default: `ASJC` options: `ASJC`, `FOR`, `FOS`, `KAKEN`, `QS`, `REF2014`, `THE`, `SDG`, `POL`	This represents the classification type of the subject area that is being looked up.

header params

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.

query params

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.

responses

status:

200

representations

application/json

Subject Area JSON Response: This is XML representing the requested document.

JSON Example

status:

200

representations

application/xml

Subject Area XML Response: This is XML representing the requested document.

XML Example

status:

200

representations

text/xml

Subject Area XML Response: This is XML representing the requested document.

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:

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

https://api.elsevier.com/analytics/scival/subjectArea/search

Subject Area Lookup API: This represents a boolean search for a SciVal Subject Area.

Methods

GET	subjectAreaSearch()

request

header params

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.

query params

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.
query	xsd:string (required)	This represents the boolean search to be executed to retrieve SciVal Subject Areas. Valid fields are name and classification. Valid operators are OR and AND. ex. query=name(biology) AND classification(ASJC)
limit	xs:int default: `100`	This value specifies the number of results to return. Coupled with offset, it can be utilized to paginate results.
offset	xs:int default: `0`	For paginating results, this is how many pages (of size = limit) to skip before returning results.