Examples are provided for documentation purposes. Live API requests require the user's own authenticated API key with the relevant verified entitlement. Example credentials must not provide access to Elsevier data or content; where live entitlement is not present, examples use synthetic or static sample responses. You can obtain your own API key using My API key.
Embed Cited by in Scopus counts (HTML fragment below)
<object height="50" data="https://api.elsevier.com/content/abstract/citation-count?doi=10.1016/S0014-5793(01)03313-0&httpAccept=text/html&apiKey=your_api_key"></object>| Name and Link | Description | |
|---|---|---|
| Article Search | Article Search is powered by ScienceDirect Search API and Serial Title API. The API response is processed by the browser in accordance with XSLT to display article citations returned by search API along with respective publication cover image returned by Serial Title API. For convenience cover images link to the corresponding publication homepage on ScienceDirect. | |
| Scopus Search | Scopus Search is powered by Scopus Search API. The search query is constructed by scoping user entered terms to Scopus all field. The API response is processed by the browser in accordance with XSLT to display article citations and cited by counts returned by Scopus Search API. |
W3C Cross-Origin Resource Sharing (CORS) spec introduces a standard
mechanism for implementing cross-domain browser requests. The CORS spec
defines a set of headers that allow the browser and server to
communicate about which requests are (and are not) allowed. CORS
support enables ease of integration with Elsevier APIs directly on your
website.
For more information about CORS please refer to http://www.w3.org/TR/cors/
and
http://enable-cors.org/.
An overview of how to leverage CORS with Elsevier APIs is
available here. You can manage
authorized CORS domains for your API keys.
We use cookies to help provide and enhance our service and tailor content.
