Elsevier Pure Web Services API — HIT Tenancy

HIT's tenancy on the Elsevier Pure web services API, deployed at scholar.hit.edu.cn/ws/api. THE RELATIONSHIP IS RECORDED HERE; THE CONTRACT IS DELIBERATELY NOT SAVED IN THIS REPO. The live document at /ws/api/openapi.json is titled "Pure API", carries contact pure-support@elsevier.com, declares a relative server of /ws/api and describes 827 paths — it is Elsevier's product specification, identical in substance across every Pure customer, and it belongs against Elsevier's own repo, not HIT's. Data paths are credential-gated (HTTP 401, Elsevier-issued api-key); there is no HIT-facing process to request one. This entry exists so the institutional fact survives without crediting HIT for Elsevier's engineering.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/elsevier-pure-tenancy"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑
aid: harbin-institute-of-technology:elsevier-pure-tenancy
name: Elsevier Pure Web Services API — HIT Tenancy
x-operator: tenant
x-surface-class: ResearchRepository
x-contract-owner: elsevier
x-tenancy:
  vendor: Elsevier
  product: Pure
  version: 5.36.2-1
  vendor_evidence: info.title "Pure API"; info.contact.email pure-support@elsevier.com; 827 paths
  dns_evidence: scholar.hit.edu.cn CNAMEs to purealb-1397755226.cn-northwest-1.elb.amazonaws.com.cn (AWS
    cn-northwest-1). Third independent confirmation of the tenancy, alongside the OpenAPI contact address
    and the OAI-PMH admin address.
description: HIT's tenancy on the Elsevier Pure web services API, deployed at scholar.hit.edu.cn/ws/api.
  THE RELATIONSHIP IS RECORDED HERE; THE CONTRACT IS DELIBERATELY NOT SAVED IN THIS REPO. The live document
  at /ws/api/openapi.json is titled "Pure API", carries contact pure-support@elsevier.com, declares a
  relative server of /ws/api and describes 827 paths — it is Elsevier's product specification, identical
  in substance across every Pure customer, and it belongs against Elsevier's own repo, not HIT's. Data
  paths are credential-gated (HTTP 401, Elsevier-issued api-key); there is no HIT-facing process to request
  one. This entry exists so the institutional fact survives without crediting HIT for Elsevier's engineering.
humanURL: https://scholar.hit.edu.cn/en/
baseURL: https://scholar.hit.edu.cn/ws/api
tags:
- Research Repository
- Pure
- Vendor Tenancy
- Scholarly
properties:
- type: Documentation
  url: https://scholar.hit.edu.cn/en/
- type: x-authentication
  url: authentication/harbin-institute-of-technology-authentication.yml