Hospitality Net APIhospitalitynet.org ↗
Retrieve full article details from Hospitality Net including headline, body HTML, authors, category, and publication timestamp via a single API endpoint.
What is the Hospitality Net API?
The Hospitality Net API exposes 1 endpoint — get_article — that returns 8 structured fields per article, including the full HTML body, writer details, article type, and ISO 8601 publication timestamp. It accepts either a full article URL or a numeric article ID, making it straightforward to retrieve content for specific pieces from this hospitality industry news platform without manual browsing.
curl -X GET 'https://api.parse.bot/scraper/eedbece5-ce28-493e-b5ed-99d1a1f35b27/get_article?article_url=https%3A%2F%2Fwww.hospitalitynet.org%2Fopinion%2F4133950%2F5-things-every-hotelier-should-know-about-pms-data-protection' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace hospitalitynet-org-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: HospitalityNet SDK — fetch an article and inspect its metadata."""
from parse_apis.hospitalitynet_org_api import HospitalityNet, InputFormatInvalid
client = HospitalityNet()
# Fetch an article by its full URL.
try:
article = client.articles.get(
article_url="https://www.hospitalitynet.org/opinion/4133950/5-things-every-hotelier-should-know-about-pms-data-protection"
)
except InputFormatInvalid as e:
print("Invalid input:", e.message)
raise
print(article.title)
print("Published:", article.date_published)
print("Category:", article.category, "| Type:", article.article_type)
print("Summary:", article.summary[:120])
# Walk the writers list — each is a typed Writer object.
for writer in article.writers:
print(f" Author: {writer.name}, {writer.position} @ {writer.organization}")
# Alternatively, fetch by numeric article ID alone.
same_article = client.articles.get(article_id="4133950")
print("By ID:", same_article.title)
print("exercised: articles.get (by url and by id)")
Get a single article's details including title, publication time, writer(s), and full content. Accepts either a full article URL or a numeric article ID. When using article_id alone, the endpoint resolves the correct article type path automatically (may require an extra redirect hop). Returns the article's HTML content, summary, category, and author information.
| Param | Type | Description |
|---|---|---|
| article_id | string | Numeric article ID, e.g. 4133950. Either article_url or article_id must be provided. When only article_id is given, the endpoint auto-resolves the article type prefix. |
| article_url | string | Full Hospitality Net article URL, e.g. https://www.hospitalitynet.org/opinion/4133950/5-things-every-hotelier-should-know-about-pms-data-protection. Either article_url or article_id must be provided. |
{
"type": "object",
"fields": {
"title": "Article headline",
"content": "Full article body as HTML",
"summary": "Brief article summary as HTML",
"writers": "Array of author objects with name, position, and organization",
"category": "Article category name such as Technology, Development",
"article_type": "Article type such as opinion, pr, explainer, opening, pipeline, renovation",
"date_published": "ISO 8601 publication timestamp"
},
"sample": {
"data": {
"title": "5 Things Every Hotelier Should Know About PMS Data Protection",
"content": "<p>Most hotels have a disaster recovery plan...</p>",
"summary": "<p>Hoteliers are urged to treat PMS outages as operational crises, with practical guidance on backup validation, offsite redundancy, and recovery drills to minimize downtime.</p>",
"writers": [
{
"name": "Doug Wagner",
"position": "Manager, Technical Services",
"organization": "Maestro"
}
],
"category": "Technology",
"article_type": "opinion",
"date_published": "2026-08-13T14:31:13.000Z"
},
"status": "success"
}
}About the Hospitality Net API
What the API Returns
The get_article endpoint retrieves a single article from Hospitality Net. A successful response includes the article title, content (full body as HTML), and summary (brief overview as HTML). It also returns a writers array, where each author object carries name, position, and organization — useful for attributing content to named industry voices or specific companies.
Input Parameters
The endpoint accepts two optional inputs, but at least one must be provided: article_url (a full URL such as https://www.hospitalitynet.org/opinion/4133950/...) or article_id (a numeric string like 4133950). When only article_id is supplied, the endpoint resolves the correct article path automatically, which may involve an internal redirect to the right article type segment.
Categorization and Metadata
Each response includes category (a topic label such as Technology or Development) and article_type (a content classification such as opinion, pr, explainer, opening, pipeline, or renovation). The date_published field is returned as an ISO 8601 timestamp, making it directly usable for sorting or filtering by recency in downstream applications.
Coverage Scope
Hospitality Net covers news, opinion, and industry reports across hotel, restaurant, and tourism sectors. The API surfaces per-article data only — there is no search, listing, or pagination endpoint in the current version. Content types span opinion pieces, press releases, explainers, opening announcements, pipeline reports, and renovation updates.
The Hospitality Net API is a managed, monitored endpoint for hospitalitynet.org — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when hospitalitynet.org changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official hospitalitynet.org API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Aggregate hospitality industry news by
article_type(e.g. only press releases or opinion pieces) for a curated feed. - Track author activity by parsing the
writersarray to monitor contributions from specific organizations. - Build a hospitality-focused content index using
date_publishedtimestamps to sort articles chronologically. - Extract
categorylabels to classify inbound articles into topic buckets like Technology or Development. - Pull full
contentHTML for text analysis or NLP pipelines targeting hotel and tourism industry language. - Monitor new hotel openings or renovation announcements by filtering on
article_typevalues like opening or renovation. - Enrich a hospitality CRM or knowledge base with structured article summaries using the
summaryfield.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Hospitality Net have an official developer API?+
What does the `writers` field return, and does it include contact information?+
writers field returns an array of author objects, each containing name, position, and organization. Contact details such as email addresses or social profiles are not included in the current response. You can fork this API on Parse and revise it to add any additional author fields that appear on the source pages.Can I retrieve a list of articles or search by keyword?+
get_article using either an article_url or article_id. There is no search, listing, or pagination endpoint. You can fork the API on Parse and revise it to add a listing or search endpoint.How fresh is the article data, and is there a publication delay?+
date_published field reflects the timestamp as recorded on the article page. The API fetches current article state at request time, so data reflects what is live on Hospitality Net at the moment of the call. There is no cached snapshot layer introducing a fixed delay.Does the API return article comments or engagement metrics?+
title, content, summary, writers, category, article_type, and date_published. Comments, view counts, or social engagement data are not part of the response. You can fork the API on Parse and revise it to add those fields if they are accessible on the article page.