FAQs
Modified on: 2025-08-07 10:32
- Q: Where can I get assistance or submit my questions?
A: For assistance or to submit questions, please email us at product.content@derbysoft.net.
- Q: Which property suppliers does DerbySoft work with?
A: DerbySoft currently connects with 35 property suppliers. You can find a complete list of our partners here: Supplier List.
- Q: What ID does DerbySoft use to identify properties when working with distributors?
A: DerbySoft uses the DerbySoft ID, which is the same as the Synxis ID.
- Q: Where can I find the documentation for the DerbySoft Distributor API?
A: You can find the documentation here: Content Distributor API.
- Q: Which OTA code mapping document does DerbySoft currently use?
A: Please refer to the doc: OTA Code.
- Q: Can you provide an example of the data we would receive?
A: Example data can be found here: Distributor API Response Samples. Please note if you have a particular request for pulling data of a property/chain, you shall send an email to Content Services- contentservices@derbysoft.net.
- Q: Can I get a sample of the Static Content Report in Excel format?
A: You can download a template of the Static Content Report in Excel here: [Template]Content_Audit_Report_Sample_EN-US. This template contains the correct formatting and can be used to prepare your data.
- Q: Do we have the ability to send room-level photos with the corresponding rate plans?
A: You can retrieve guestroom images through the Distributor API, specifically via the GuestRooms.GuestRoom.MultimediaDescriptions.MultimediaDescripition.ImageItems path. For details please refer to the Hotel Descriptive Info.- Details and code mappings for image categories (using the ImageItem.@Category field) can be found in OTA_CodeType_en-US tab of the Hotel Descriptive Info.
- Please note that due to the way our content API is structured, a direct one-to-one mapping between room types and rate plans is not currently available.
- Q: Can you support JSON format to replace XML format in API request/response body?
A: Currently, our API uses XML for requests and responses. JSON format is not yet supported.
Did you find it helpful? Yes No
Send feedback