This represents the search and retrieval interfaces associated with Embase. This represents a search against the EMBASE content. 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. 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. This represents a unique application developer key providing access to API resources. This key can also be submitted as the query string parameter "apiKey" 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". 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". 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. Override for HTTP header Accept, this represents the acceptable mime types in which the response can be generated. 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. 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. Override for HTTP header X-ELS-APIKey, this represents a unique application developer key providing access to resource. 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.
This represents the boolean search to be executed against the EMBASE content. The query should be provided in CommandLanguage syntax. One of parameters query or alertid is required

ex. query=heart+attack%20AND%20mati
The encoded alert Id. Query is taken from the corresponding alert. Represents base64 string, which can be found e.g. in email alert. Should be url encoded. One of parameters query or alertid is required.
Numeric value representing the results position (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 1 (i.e. first search result)

ex. start=5
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
The sorting option for the results returned.

ex. sort=entrydate This is XML representing the requested resource. This is XML representing the requested resource. This is an error that occurs when invalid information is submitted. This is an error that occurs when a user cannot be authenticated due to missing/invalid credentials (authtoken or APIKey). This is an error that occurs when a user cannot be authenticated or entitlements cannot be validated. This is an error that occurs when the request resource cannot be found. This is an error that occurs when the requested HTTP Method is invalid. This is an error that occurs when the requested mime type is invalid. This is an error that occurs when a requester has exceeded the quota limits associated with their API Key. This is a general purpose error condition, typically due to back-end processing errors. This represents an article retrieval using a LUI (internal identifier). 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. 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. This represents a unique application developer key providing access to API resources. This key can also be submitted as the query string parameter "apiKey" 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". 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". 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. Override for HTTP header Accept, this represents the acceptable mime types in which the response can be generated. 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. 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. Override for HTTP header X-ELS-APIKey, this represents a unique application developer key providing access to resource. 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. This is XML representing the requested document. This is XML representing the requested document. This is an error that occurs when invalid information is submitted. This is an error that occurs when a user cannot be authenticated due to missing/invalid credentials (authtoken or APIKey). This is an error that occurs when a user cannot be authenticated or entitlements cannot be validated. This is an error that occurs when the request resource cannot be found. This is an error that occurs when the requested HTTP Method is invalid. This is an error that occurs when the requested mime type is invalid. This is an error that occurs when a requester has exceeded the quota limits associated with their API Key. This is a general purpose error condition, typically due to back-end processing errors. This represents an article retrieval using a PII (Publication Item Identifier). 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. 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. This represents a unique application developer key providing access to API resources. This key can also be submitted as the query string parameter "apiKey" 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". 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". 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. Override for HTTP header Accept, this represents the acceptable mime types in which the response can be generated. 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. 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. Override for HTTP header X-ELS-APIKey, this represents a unique application developer key providing access to resource. 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. This is XML representing the requested document. This is XML representing the requested document. This is an error that occurs when invalid information is submitted. This is an error that occurs when a user cannot be authenticated due to missing/invalid credentials (authtoken or APIKey). This is an error that occurs when a user cannot be authenticated or entitlements cannot be validated. This is an error that occurs when the request resource cannot be found. This is an error that occurs when the requested HTTP Method is invalid. This is an error that occurs when the requested mime type is invalid. This is an error that occurs when a requester has exceeded the quota limits associated with their API Key. This is a general purpose error condition, typically due to back-end processing errors. This represents an article retrieval using a DOI (Document Object Identifier). 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. 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. This represents a unique application developer key providing access to API resources. This key can also be submitted as the query string parameter "apiKey" 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". 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". 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. Override for HTTP header Accept, this represents the acceptable mime types in which the response can be generated. 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. 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. Override for HTTP header X-ELS-APIKey, this represents a unique application developer key providing access to resource. 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. This is XML representing the requested document. This is XML representing the requested document. This is an error that occurs when invalid information is submitted. This is an error that occurs when a user cannot be authenticated due to missing/invalid credentials (authtoken or APIKey). This is an error that occurs when a user cannot be authenticated or entitlements cannot be validated. This is an error that occurs when the request resource cannot be found. This is an error that occurs when the requested HTTP Method is invalid. This is an error that occurs when the requested mime type is invalid. This is an error that occurs when a requester has exceeded the quota limits associated with their API Key. This is a general purpose error condition, typically due to back-end processing errors. This represents an article retrieval using Embase Accession Number. 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. 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. This represents a unique application developer key providing access to API resources. This key can also be submitted as the query string parameter "apiKey" 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". 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". 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. Override for HTTP header Accept, this represents the acceptable mime types in which the response can be generated. 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. 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. Override for HTTP header X-ELS-APIKey, this represents a unique application developer key providing access to resource. 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. This is XML representing the requested document. This is XML representing the requested document. This is an error that occurs when invalid information is submitted. This is an error that occurs when a user cannot be authenticated due to missing/invalid credentials (authtoken or APIKey). This is an error that occurs when a user cannot be authenticated or entitlements cannot be validated. This is an error that occurs when the request resource cannot be found. This is an error that occurs when the requested HTTP Method is invalid. This is an error that occurs when the requested mime type is invalid. This is an error that occurs when a requester has exceeded the quota limits associated with their API Key. This is a general purpose error condition, typically due to back-end processing errors. This represents an article retrieval using a MEDLINE PubMed Identifier. 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. 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. This represents a unique application developer key providing access to API resources. This key can also be submitted as the query string parameter "apiKey" 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". 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". 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. Override for HTTP header Accept, this represents the acceptable mime types in which the response can be generated. 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. 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. Override for HTTP header X-ELS-APIKey, this represents a unique application developer key providing access to resource. 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. This is XML representing the requested document. This is XML representing the requested document. This is an error that occurs when invalid information is submitted. This is an error that occurs when a user cannot be authenticated due to missing/invalid credentials (authtoken or APIKey). This is an error that occurs when a user cannot be authenticated or entitlements cannot be validated. This is an error that occurs when the request resource cannot be found. This is an error that occurs when the requested HTTP Method is invalid. This is an error that occurs when the requested mime type is invalid. This is an error that occurs when a requester has exceeded the quota limits associated with their API Key. This is a general purpose error condition, typically due to back-end processing errors. This represents an article retrieval using a MEDLINE PubMed Identifier. 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. 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. This represents a unique application developer key providing access to API resources. This key can also be submitted as the query string parameter "apiKey" 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". 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". 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. Override for HTTP header Accept, this represents the acceptable mime types in which the response can be generated. 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. 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. Override for HTTP header X-ELS-APIKey, this represents a unique application developer key providing access to resource. 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. This is XML representing the requested document. This is XML representing the requested document. This is an error that occurs when invalid information is submitted. This is an error that occurs when a user cannot be authenticated due to missing/invalid credentials (authtoken or APIKey). This is an error that occurs when a user cannot be authenticated or entitlements cannot be validated. This is an error that occurs when the request resource cannot be found. This is an error that occurs when the requested HTTP Method is invalid. This is an error that occurs when the requested mime type is invalid. This is an error that occurs when a requester has exceeded the quota limits associated with their API Key. This is a general purpose error condition, typically due to back-end processing errors.