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

Johns Hopkins University Taxonomy API

Taxonomy endpoints: the vocabularies used to categorize and attribute Hub content.

Johns Hopkins University Taxonomy API is one of 9 APIs that Johns Hopkins University publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 27 operations across 27 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 1.

Requests are made against a single base URL, https://api.hub.jhu.edu.

27 operations 27 paths 5 schemas 27 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1
Base URL
https://api.hub.jhu.edu
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Johns Hopkins University Taxonomy API declares 1 security scheme for authenticating requests. An API key is passed in the query as key (apiKey). By default, every request must be authenticated.

  • apiKey — API key issued by the Hub API team. Johns Hopkins affiliates request a key by email; the API is not open to the general public.

Paths & Operations 27

Across 27 paths, the API surfaces 27 operations — 27 GET. Each is listed below with its method, path, parameters, and response codes.

Taxonomy 27

Taxonomy endpoints: the vocabularies used to categorize and attribute Hub content.

GET
/announcement_categories
Get a collection of announcement categorys
listAnnouncementCategories 8 params → 200401404
GET
/announcement_categories/{id}
Get one announcement category
getAnnouncementCategorie 4 params → 200401404
GET
/announcement_categories/{id}/{subcollection}
Get a subcollection of one announcement category
getAnnouncementCategorieSubcollection 7 params → 200401404
GET
/channels
Get a collection of channels
listChannels 8 params → 200401404
GET
/channels/{id}
Get one channel
getChannel 4 params → 200401404
GET
/channels/{id}/{subcollection}
Get a subcollection of one channel
getChannelSubcollection 7 params → 200401404
GET
/divisions
Get a collection of divisions
listDivisions 8 params → 200401404
GET
/divisions/{id}
Get one division
getDivision 4 params → 200401404
GET
/divisions/{id}/{subcollection}
Get a subcollection of one division
getDivisionSubcollection 7 params → 200401404
GET
/event_categories
Get a collection of event categorys
listEventCategories 8 params → 200401404
GET
/event_categories/{id}
Get one event category
getEventCategorie 4 params → 200401404
GET
/event_categories/{id}/{subcollection}
Get a subcollection of one event category
getEventCategorieSubcollection 7 params → 200401404
GET
/faculty_expert_affiliations
Get a collection of faculty expert affiliations
listFacultyExpertAffiliations 8 params → 200401404
GET
/faculty_expert_affiliations/{id}
Get one faculty expert affiliation
getFacultyExpertAffiliation 4 params → 200401404
GET
/faculty_expert_affiliations/{id}/{subcollection}
Get a subcollection of one faculty expert affiliation
getFacultyExpertAffiliationSubcollection 7 params → 200401404
GET
/faculty_expert_topics
Get a collection of faculty expert topics
listFacultyExpertTopics 8 params → 200401404
GET
/faculty_expert_topics/{id}
Get one faculty expert topic
getFacultyExpertTopic 4 params → 200401404
GET
/faculty_expert_topics/{id}/{subcollection}
Get a subcollection of one faculty expert topic
getFacultyExpertTopicSubcollection 7 params → 200401404
GET
/locations
Get a collection of locations
listLocations 8 params → 200401404
GET
/locations/{id}
Get one location
getLocation 4 params → 200401404
GET
/locations/{id}/{subcollection}
Get a subcollection of one location
getLocationSubcollection 7 params → 200401404
GET
/tags
Get a collection of tags
listTags 8 params → 200401404
GET
/tags/{id}
Get one tag
getTag 4 params → 200401404
GET
/tags/{id}/{subcollection}
Get a subcollection of one tag
getTagSubcollection 7 params → 200401404
GET
/topics
Get a collection of topics
listTopics 8 params → 200401404
GET
/topics/{id}
Get one topic
getTopic 4 params → 200401404
GET
/topics/{id}/{subcollection}
Get a subcollection of one topic
getTopicSubcollection 7 params → 200401404

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Collection (6 properties), Resource (4 properties), Links (4 properties), Error (3 properties). Each schema is shown below with its type and property counts.

Collection
object
A HAL collection response. The requested resources are carried inside embedded, keyed by the plural resource name.
6 properties
Error
object
3 properties 3 required
Links
object
An object that contains links to related resources.
4 properties
Resource
object
A HAL object response containing a single resource. Resource data points vary by resource type; id and type are present on every resource.
4 properties
Link
object
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

johns-hopkins-university-taxonomy-api-openapi.yml Raw ↑

Other APIs Johns Hopkins University publishes across the network.

Johns Hopkins University SIS Classes API
Johns Hopkins University SIS Codes API
JHU API Portal (MuleSoft Anypoint)
Johns Hopkins Shibboleth Identity Provider
Project MUSE OAI-PMH Repository
Johns Hopkins Research Data Repository
Johns Hopkins Research Portal (Elsevier Pure tenancy)
Johns Hopkins University Content API
Where this information came from

This is an independent, third-party profile of Johns Hopkins University Taxonomy 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.