Properties
| Name | Type | Description |
|---|---|---|
| _metadata | object | |
| _metadata.links | array | |
| _metadata.links[].rel | string | rel link |
| _metadata.links[].href | string | href link |
| _metadata.totalItems | number | Total number of items returned. |
| items | array | All updates, available at all cases |
| items[].updatesText | string | Updated text |
| items[].updatedAtTimestamp | string | Timestamp when the update occurred |
| items[].asDate | string | Timestamp when the update occurred |
| items[].practiceChangingUpdate | boolean | Is this a practice changing update |
| items[].updatePriority | string | Update priority |
| items[].updateType | string | Update type |
| items[].relevantTopics | array | |
| items[].relevantTopics[].id | string | Id for the topic |
| items[].relevantTopics[].anchor | string | Link to the update within the topic |
| items[].relevantTopics[].practiceChangingUpdate | boolean | Is this a practice changing update |
| items[].relevantTopics[].slug | string | Slug of the topic - this gets appended to the domain ex: www.dynamed.com/slug |
| items[].relevantTopics[].title | string | Title of the topic |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/ebsco/main/json-schema/ebsco-get-content-change-alerts-response-schema.json",
"title": "GetContentChangeAlertsResponse",
"x-generated": "2026-10-14",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/_ae-authored/ebsco-openapi-generated.yml#/components/schemas/GetContentChangeAlertsResponse",
"type": "object",
"properties": {
"_metadata": {
"type": "object"
},
"_metadata.links": {
"type": "array"
},
"_metadata.links[].rel": {
"type": "string",
"description": "rel link"
},
"_metadata.links[].href": {
"type": "string",
"description": "href link"
},
"_metadata.totalItems": {
"type": "number",
"description": "Total number of items returned."
},
"items": {
"type": "array",
"description": "All updates, available at all cases"
},
"items[].updatesText": {
"type": "string",
"description": "Updated text"
},
"items[].updatedAtTimestamp": {
"type": "string",
"description": "Timestamp when the update occurred"
},
"items[].asDate": {
"type": "string",
"description": "Timestamp when the update occurred"
},
"items[].practiceChangingUpdate": {
"type": "boolean",
"description": "Is this a practice changing update"
},
"items[].updatePriority": {
"type": "string",
"description": "Update priority"
},
"items[].updateType": {
"type": "string",
"description": "Update type"
},
"items[].relevantTopics": {
"type": "array"
},
"items[].relevantTopics[].id": {
"type": "string",
"description": "Id for the topic"
},
"items[].relevantTopics[].anchor": {
"type": "string",
"description": "Link to the update within the topic"
},
"items[].relevantTopics[].practiceChangingUpdate": {
"type": "boolean",
"description": "Is this a practice changing update"
},
"items[].relevantTopics[].slug": {
"type": "string",
"description": "Slug of the topic - this gets appended to the domain ex: www.dynamed.com/slug"
},
"items[].relevantTopics[].title": {
"type": "string",
"description": "Title of the topic"
}
}
}
Work with this as data
Every JSON Schema 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 schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.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.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/ebsco-get-content-change-alerts-response"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
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.