How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Elsevier Engineering Village API

Engineering Village APIs provide programmatic access to engineering research literature, indexed publications, and engineering-focused content across multiple databases.

Elsevier Engineering Village API is one of 10 APIs that Elsevier publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Engineering and Research. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 2 operations across 2 paths, organized into 2 resource areas, and defines 19 schemas. It is described by OpenAPI 2.0, at version 2.0.

Requests are made against the base URL https://api.elsevier.com/content.

2 operations 2 paths 19 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 2.0
API Version
2.0
Base URL
https://api.elsevier.com/content
Resource Areas
2

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 GET. They span 2 resource areas: Engineering_Village_Search, Engineering_Village_Retrieval. Each is listed below with its method, path, parameters, and response codes.

Engineering_Village_Search 1

Engineering Village Search API

GET
/ev/results
Engineering Village Search API
expertSearchUsingGET 15 params → 200400401500403429
Engineering_Village_Retrieval 1

Engineering Village Retrieval API

GET
/ev/records
Engineering Village Retrieval API
fetchRecordUsingGET 4 params → 200400401500403429

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are CitationEiDoc (9 properties), ContributorInfo (5 properties), DocID (4 properties), PageContainerItems (3 properties). Each schema is shown below with its type and property counts.

PageContainer
object
1 property
Status
object
2 properties
DocID
object
4 properties
ServiceError
object
1 property
PageContainerItems
object
3 properties
PageResults
object
1 property
FT
object
1 property
DocProperties
object
1 property
Afs
object
1 property
CitationEiDoc
object
9 properties
PageEntry
object
1 property
Efs
object
1 property
ContributorInfo
object
5 properties
Eds
object
1 property
Database
object
2 properties
ServiceErrorWrap
object
1 property
Aus
object
1 property
ContributorAffiliation
object
1 property
Affiliation
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

elsevier-engineering-village-swagger.json Raw ↑

Other APIs Elsevier publishes across the network.

Elsevier Scopus APIs
Elsevier ScienceDirect APIs
Elsevier SciVal API
Elsevier Embase API
Elsevier Retrieval APIs
Elsevier Metadata APIs
Elsevier COUNTER SUSHI API
Elsevier Abstract API
Elsevier Search API
Where this information came from

This is an independent, third-party profile of Elsevier Engineering Village API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.