Making property onboarding easier
Transforming the current Content API into new modular APIs
The Content API is essential for listing properties at scale on Tripeden.com, allowing your connected properties to create and modify room and property content directly within your interface. It is part of the foundational solutions for homes and vacation rentals, addressing their basic needs.
Through modularisation, we’re breaking down our legacy solution and developing a set of smaller, modular RESTful JSON APIs to better align with the evolving needs of our hospitality partners.
The Content API - including HDCN, HSN, HDI for Homes, HIN for Homes, and House Rules API* - entered its deprecation phase at the end of 2024 and will be discontinued by the end of 2026. Continue reading to learn how this change will affect Homes, Core, and Chain Providers.
[Last updated May 2025]
What’s covered
The benefits of modularising the Content API
The new modular APIs
API bundles you can implement
How to implement these APIs
Deprecation of the existing Content API
Connectivity Partner Programme (CPP) benefits
The benefits of modularising the Content API
 |  |  |
| Simplified structure | Efficiency | Flexibility |
| Small, modern APIs that are easy to implement and use | Seamless onboarding that provides extranet parity to your properties | Implement only what you need to support your business |
The new modular APIs
Get to know a little more about our new APIs and start your implementations
- Property API (Property Details endpoint, Property Setting endpoint and Property Status Manager)
- Contacts API
- Facilities API
- Charges API
- Room API
Property Details endpoint 
Create and update basic information to obtain a unique property ID. Manage details including the name, address (with latitude and longitude), check-in and check-out times, languages, property type, currency, star rating, and URL.
Status: Live 🟢
You can access the scope and field list by logging in and navigating to Resources then finding the Download section. From there, select Marketing Assets.
Property Settings endpoint 
Control the types of guests who can book your accommodation, as well as oversee your financial and tax configurations. Manage policies for pets, children, house rules, fine print, booking requests, damage protection, invoices, and tax settings.
Status: Live 🟢
You can access the scope and field list by logging in and navigating to Resources then finding the Download section. From there, select Marketing Assets.
Property Status Manager 
Manage properties by opening or closing them, capturing reasons for closures, verifying that properties meet open and bookable requirements, and retrieving any errors or warnings that identify the necessary criteria to open a property.
Status: Live 🟢
You can access the scope and field list by logging in and navigating to Resources then finding the Download section. From there, select Marketing Assets.
Contacts API 
You can create, update, and delete property contact details seamlessly. Manage all your contacts and related information, including names and addresses, for multiple contact types.
Status: Live 🟢
You can access the scope and field list by logging in and navigating to Resources then finding the Download section. From there, select Marketing Assets.
Facilities API 
Create and manage facilities for properties and rooms, including temporary closure dates and more.
Status: Live 🟢
You can access the scope and field list by logging in and navigating to Resources then finding the Download section. From there, select Marketing Assets.
Charges API 
Easily set and manage taxes and fees for properties and its rooms that are part of the reservation, regardless of property status.
Status: Live 🟢
You can access the scope and field list by logging in and navigating to Resources then finding the Download section. From there, select Marketing Assets.
Room API 
Create and oversee rooms, room configurations, and sub-rooms. Manage room types, including room names, room size, occupancy, beds, and bedding arrangements.
Status: Live 🟢
You can access the scope and field list by logging in and navigating to Resources then finding the Download section. From there, select Marketing Assets.
Policies API 
Create, modify, retrieve, and manage cancellation and prepayment policies for properties.
Status: Live 🟢
We have made it easier to migrate to the new modular APIs
We know that migrating can be challenging due to the legacy API, which has several limitations:
- One XML node contains information pertaining to multiple data domains.
- Removing a single node affects multiple domains and the new APIs alike.
This complexity hindered gradual migration. So, we’ve made it easier for you to move from HotelDescriptiveContentNotif (HDCN) property management endpoint to the new APIs.
Introducing the domain_update_lock feature to support a smooth migration: A Data Domain represents a subset of fields related to the same topic (facilities, contacts, charges, etc) that should be managed separately. In HDCN, however, unrelated fields were stored in a single XML node, a problem that has been resolved in the new APIs.
For example, Charges represent the taxes and fees that appear on a reservation:
- Tax policies in the HDCN are now part of the Charges data domain, which is managed via the Charges API
- Fee policies in the HDCN are also included in the Charges data domain and are managed via the Charges API, except in the following cases:
- ChildrenPolicy-related FeePolicies: 37, 38, 44 are now managed through the Property Settings API
- Parking FeePolicy: 5035, Internet policy: 5036 are now managed through the Facilities API
If you remove the fee policies node it will delete information related to three different data domains, each which is now served by distinct APIs. To prevent this, we’ve introduced a series of domain update lock features that gives you the flexibility to migrate gradually and confidently:
- You inform Tripeden.com that you have implemented the new API (e.g. Charges) while continuing to use HDCN for other information.
- We then do not process any information sent in HDCN that exists in the charges domain, managing it instead through the Charges API.
To activate these features, please log in to the provider portal and follow these steps:
Access: connect.tripeden.com -> Administration -> Feature Management -> domain_update_lock_<feature name>.
API bundles you can implement
 | |
Bundle 1: All new APIs If you want to create and open a property on Tripeden.com, you need all of the new modules (in addition to already modularised APIs such as the Photo API, Licences API and Contracting) | Bundle 2: Content management bundle If you want to optimise property content, you only need specific modules, including the Facilities API, Property Settings endpoint and Photo API (already an existing API) |
How to implement these APIs
Option 1: Implement altogether
Implement all required APIs together. If you prefer to migrate to the new APIs all at once rather than one by one, you can implement all the APIs now. We have been told by beta providers that this migration approach is easier than having to manage properties via the new APIs and the existing Content API at the same time.
Option 2: Implement modules individually when they are live.
If you don’t currently use the Content API, you can implement them one by one and gradually add what is needed for you from the new modules.
If you already have the Content API, you should consider implementing the APIs or endpoints one by one if you frequently update specific types of information.
When to implement one by one
|  | | |
Contacts API Your properties frequently update contact information. Considerations: Low latency (0.5 sec), no UI changes needed, fast implementation times. | Property Details endpoint Your properties frequently update property name, latitude/longitude, check-in, check out times, star rating languages spoken. Considerations: Low latency, no UI changes needed, fast implementation times. | Property Settings endpoint Your properties want to change the type of guests they want to attract by updating house rules, fine print/standard phrases, child and pet policies. Opt into request to book or Booking’s damage program or update invoice/finance settings | Facilities API Your properties frequently update facilities. This offers extranet parity and allows you to add details about the facilities. There is no longer an overlay so facilities would not be removed in error. |
Deprecation of the existing Content API
The Content API - including HDCN, HSN, HDI for Homes, HIN for Homes, and House Rules API - has entered its deprecation phase. During this period, no new features will be added, and the API will be in maintenance mode until it's sunsetted at the end of 2026. From the end of 2024:
- HDCN, HSN, HDI APIS entered deprecation at the end of 2024 and there will be no new implementation post the end of 2024 by any of our connectivity providers (exceptions may apply if implementation is already very far advanced).
- For HIN endpoint, there will be no new Home provider implementations post end of 2024. For Core and Chains, the implementation of HIN may continue, if preferred over the new Rooms API.
* Content API acronyms, explained:
HDCN: HotelDescriptiveContentNotif
HSN: HotelSearch
HDI: HotelDescriptiveInfo
HIN: HotelInvNotif
Connectivity Partner Programme (CPP) benefits
Your performance in the Connectivity Solutions pillar of the CPP 2025 is measured by your adoption of foundational solutions.
The new modules are categorised as foundational solutions in the CPP 2025 for partners within the Homes segment. During this transition year, the existing Content API remains foundational. Log in and go to Resources, select Download, then CPP guide for 2025 to learn more.
FAQ
Should I implement all APIs together or can I do it one by one?
Consider what works best for your business. You can wait and build all at once when the APIs are fully delivered or as soon as each is launched to take advantage of the benefits immediately. To help make it easier for you to decide, we’ll identify which specific APIs are necessary to achieve certain goals, such as making a property open/bookable. We’ll share more information on this soon, together with options for integration.
When will I have to stop using Content API endpoints?
We’re working on a timeline and will be able to confirm soon. We expect to maintain the endpoints until 2026 and will adjust if we’re delayed with the delivery of new APIs. We’ll deprecate and sunset everything together, rather than a gradual deprecation based on the delivery of each new API, as you may want to wait before implementing them. We recommend implementing the new APIs when they become available as they will deliver benefits as well as new products and features.
What if I don't want to migrate from the Content API?
Unfortunately this isn’t an option. Content API endpoints will eventually be permanently removed.
How will you help us with migration?
We’ll provide you with clear documentation and information on:
- Descriptions and purposes of each new API and endpoint.
- Mapping of old fields to new fields, in case you need to alter existing data tables to store or share information for your UI.
- Any field renaming or changes to the database.
- Changes to validations moved to another API and considerations for building the workflow.
- New product improvements and what they enable you to do.
I’m currently implementing the Content API. Should I stop implementation?
This depends on the needs of your business. We recommend that everyone continues implementing the APIs that are already modular, such as the Photo API, Contracting API, Licences API, Property Profile API and Key Collection API.
You can check the deprecation section on this page for more information on timelines. We will continue to update this section with additional information on what you can expect between now and sunsetting timelines.
If you choose to implement the current Content API, please note that we will continue supporting it until 2026.
How does this affect my Connectivity Partner Programme (CPP) status?
Your performance in the Connectivity Solutions pillar of the CPP 2025 is measured by your adoption of foundational solutions.
The new modules are categorised as foundational solutions in the CPP 2025 for partners within the Homes segment. During this transition year, the existing Content API remains foundational. Please refer to the CPP guide for 2025 to know more.
Are there more details about the other new APIs and endpoints?
These are still in development and we plan to release them later in 2024. We will update this page with more information closer to their official launch dates.
Will authentication stay the same?
Yes.
Do these APIs require certification?
If you’re migrating and are already CAPI-certified (PROD): don’t need the below if you have it already.
If you’re not CAPI-certified, you’ll need to do the following:
- Follow the tutorials in the documentation to get a Response Unique IDentifier (RUID) certification check for each relevant module
Send the RUIDs to the support team and get certified in accordance with the normal SLAs.
What pathway is Tripeden.com planning to take in terms of connectivity specifications?
We’ll stop supporting a large HDCN endpoint when building the new APIs. Instead, we plan to build a set of smaller, modularised JSON APIs. We will, however, try to follow the existing Content API request structure where possible in order to simplify future migrations for Connectivity partners. We’ll share migration guides soon.
