Best practices for file ingestion

When you’re building out your system to pull in data from Expedia, following this advice will get you the best results.

File format

Use column name, not column order

Pulling data by column name means that you can add or remove columns more easily, and you won’t have to worry about changes in field order in a new file.

Don’t require records to be in a specific order

Self-serve reporting options don’t support record sorting and are not sorted in any specific order.

Don’t require files to be in a specific order

If there’s a delay or defect in one day’s file, it won’t impact future file ingestions while a fix is in progress.

Field values

Don’t limit field character lengths

With no maximum value, you’ll have more flexibility for longer character limits in the future, without need for redevelopment.

Limit custom data types

Keeping the types of data included to only text, number, or date ensures flexibility. If other data types are required, the schemas provided have the recommended minimum length.

Don’t restrict on a specific list of values

If new values are introduced, keeping the list of values unrestricted keeps the need for redevelopment low. Although some fields appear to have set values, such as payment_type and booking_item_status, we may add new ones as needs change. When changes happen, we won’t remove any existing values, so that we ensure backwards compatibility.

Validate mandatory fields before beginning ingestion

We don’t support the generation of partial files. If there are fields that your system requires, be sure to validate that the file is complete before starting its ingestion.

Allow for special characters

This setting allows for more flexibility, because hotel names and locations may include special characters.

Don’t restrict text fields based on case

Allowing both upper and lower case in text fields will make ingestion more flexible. If a specific text case is required, you can add logic to make the field in question all upper or lower case as the file is ingested.

File pickup (SFTP)

Use the Expedia SFTP server

We recommend using an Expedia server to transfer files. This access allows us to provide high levels of security, and allows our staff to troubleshoot should any issues arise. You can add the Expedia SFTP server to your allow list for smooth interactions.

If your organization requires ownership of the SFTP server, talk with your account manager.

Flexible file placement timelines

With less-rigid timelines you won’t need to police the file placement as closely. For example, 99% of the time, a placement window of 9:00 am to 3:00 pm PST (4:00 pm to 10:00 pm UTC) is precise enough. We recommend that you set up a process to alert you when a file hits the SFTP server.