Is Airbnb API Down Right Now? Discover if there is an ongoing service outage.

We are currently investigating an issue that begun on 2025-06-30 around 1:00 PM PDT impacting the creation and updating of Seasonal Rule Sets, as well as LOS Records. Further updates will be provided as we progress in resolving this issue.

We are currently investigating an issue that had begun on 2025-06-18, affecting a subset of reservation webhook notifications where the thread_id is not populated in the reservation object. As a result, some webhook notifications may experience delivery delays. Please note that this issue does not impact all reservation webhook notifications but is limited to a small subset. We recommend utilizing the GET reservations API to retrieve the necessary data for your system. Further updates will be provided as we progress in resolving this issue.

We are currently investigating an issue that had begun on 2025-06-18, affecting a subset of reservation webhook notifications where the thread_id is not populated in the reservation object. As a result, some webhook notifications may experience delivery delays. Please note that this issue does not impact all reservation webhook notifications but is limited to a small subset.We recommend utilizing the GET reservations API to retrieve the necessary data for your system.Further updates will be provided as we progress in resolving this issue.

This incident has been resolved. If you are still encountering problems, please reach out to us via the Support Portal.

We are investigating an incident impacting requests to the listing descriptions API. This issue started around 2025-06-03, 07:00 PDT and may result in listing's page to display the description encoded. We will share more updates as soon as possible.

We are investigating an incident impacting requests to the listing descriptions API. This issue started around 2025-06-03, 07:00 PDT and may result in listing's page to display the description encoded. We will share more updates as soon as possible.

The issue has been resolved. Please retry any failed requests during this incident. We apologize for the inconvenience.

We implemented a fix for the issue as of 14:35 PDT May 23rd, and are now monitoring the results.

We are investigating an incident impacting requests to the calendar API. This issue started around 13:35 PDT and may result in the async calendar requests failing with 403 errors. We will share more updates as soon as possible.

We are investigating an incident impacting requests to the calendar API. This issue started around 13:35 PDT and may result in the async calendar requests failing with 403 errors. We will share more updates as soon as possible.

The issue has been resolved. Please retry any failed requests during this incident. We apologize for the inconvenience.

We implemented a fix for the issue as of 18:00 PDT, and are now monitoring the results.

We are investigating an incident impacting Airbnb and the API. This issue started around 16:00 PDT and may result in 500 errors across our endpoints and the Airbnb website. We will share more updates as soon as possible.

We are investigating an incident impacting Airbnb and the API. This issue started around 16:00 PDT and may result in 500 errors across our endpoints and the Airbnb website. We will share more updates as soon as possible.

We experienced an increased number of 500 Errors impacting mainly the POST listing_photos requests. This started on 2025-04-29 17:00 PM PST and was eventually resolved on 2025-04-29 21:00 PM PST. Please check and retry the listing photo uploads for the listings that may have been affected by this incident. OR Please check the affected listings' photos and retry the photo uploads as required.

We experienced an increased number of 500 Errors impacting mainly the POST listing_photos requests. This started on 2025-04-29 17:00 PM PST and was eventually resolved on 2025-04-29 21:00 PM PST.Please check and retry the listing photo uploads for the listings that may have been affected by this incident.ORPlease check the affected listings' photos and retry the photo uploads as required.

This incident has been resolved. Please create a new support case if you still encounter issues.

We deployed a fix for this issue today, April 24, at 10:00 AM (PDT), and we're currently monitoring the results.

Our team has identified a problem where portions of the Partner Portal may not be loading correctly. We'll share further updates as soon as possible.

This incident has been resolved. Please create a new support case if you still encounter issues.

We deployed a fix for this issue today, April 24, at 10:00 AM (PDT), and we're currently monitoring the results.

Our team has identified a problem where portions of the Partner Portal may not be loading correctly. We'll share further updates as soon as possible.

The issue has been identified, and a fix has been deployed.

Our team is currently investigating a problem where portions of the Partner Portal may not be loading correctly. We'll share further updates as soon as possible.

The issue has been resolved. If you are still encountering problems, please reach out to us through the Support Portal.

We launched a fix for this issue on March 31 at 3:00 PM (PDT) and will monitor the results. The issue started on March 30 at 11:30 PM (PDT). It caused listings to stay API-connected after a Host disconnected from an application. You may have experienced this error when attempting to API-connect a listing, the error message says: "This listing is connected to a different API partner" when trying to API-connect a listing. If you still facing this error, please contact us through the Support Portal.

We are looking into reports that listings stay API-connected after a Host disconnects from an application. Our team is working on this issue and will share updates when we have more information.

There was an issue that resulted in a higher number of 500 errors on the Listings API, from approximately Mar 12, 8:00 PM to 9:30 PM PDT. This issue has been resolved. Please retry any failed requests. If you are still encountering problems, please reach out to us through the Support Portal.

This incident has been resolved as of March 5, 2025 around 22:15 PM (PST). Please retry any failed requests again. Please also ensure that all API requests contain the necessary headers. We apologize for the inconvenience this incident may have caused.

A fix has been implemented on March 5, 2025 around 22:15 PM (PST). We expect the 420 Errors to stop now, please retry the failed requests again and ensure that they contain the necessary headers. Please do let us know via the Partner Support Portal if still encountering 420 Errors.

We are looking into an issue where some API requests are failing with a 420 error. This error started on March 4, 2025, around 11:00 AM (PT). While we investigate, please ensure that your API requests contain all the necessary headers as listed on the following guide: https://developer.airbnb.com/docs/authentication-and-encryption We will post more updates as soon as possible.

The issue has been resolved. If you are still encountering problems, please reach out to us through the Support Portal.

This issue has been mitigated as of Tuesday, Feb 11th at 6:15 PM PST. We apologize for the inconvenience.

We have discovered an issue that is resulting in a higher number of 500 errors on the Listings API. Our team is actively working on a solution. This issue began on Feb 11 at approximately 10:00 AM (PT). We will provide further updates as soon as they become available.

This issue has been mitigated as of Monday, Feb 10th at 7:15 PM PST. Please proceed with re-sending any requests impacted by this incident. We apologize for the inconvenience.

A fix has been implemented and has mitigated the issue. We will monitor the status and provide further updates if any. Thank you for your patience and understanding.

We have identified the issue and are currently working on a resolution. In the meantime, please try resending your failed requests. We apologize for any inconvenience this may have caused.

We are actively investigating an increased number of 500 errors across multiple endpoints, mainly the Pricing Settings endpoints. We'll share further updates as soon as possible.

This issue has been mitigated as of Wednesday, Jan 29th at 11:30 PM (PST). Please proceed with authorizing any Hosts who were impacted due to this incident. We apologize for the inconvenience.

A fix has been implemented and we are monitoring the results.

Our team is still working to resolve this issue. Meanwhile, please recommend Hosts to have their Airbnb account's email address, phone number, and government ID verified and that they have uploaded a profile picture before they try to authorize your application.

We're looking into an issue affecting the authorization flow. Hosts without verification information are being redirected to the Airbnb homepage, which prevents the authorization process from completing. While we investigate, please remind all hosts authorizing your application to ensure their Airbnb accounts include the following information: - Profile picture - Verified email address - Verified phone number - Government ID We'll share further updates as soon as possible.

This incident has been resolved.

Our team is currently addressing a problem where the listings dashboard and/or overview page may not be loading correctly. We'll share further updates as soon as possible.

This incident has been resolved.

We deployed a fix for this issue around 11:45AM (PT) and the issue has been resolved. We will keep monitoring the results.

We are currently investigating issues with new reservations not populating in the Partner Portal Reservations Dashboard and also not being returned in the GET all reservations request response. Reservation confirmation webhooks are still being delivered as expected. You may still retrieve the specific reservation with a GET reservations request. We'll share further updates as soon as possible.

This issue has been resolved.

Our team is currently addressing a problem where API requests aren't being logged in the Partner Portal. Please note that these API requests are being processed correctly; they're just not being displayed in the Partner Portal. We'll share further updates as soon as possible.

This incident has been resolved. If you are still experiencing this issue, please contact us via the Support Portal.

A fix has been implemented for the issue; image URLs in Messaging API and webhooks should work as expected now.

Our team is currently addressing an issue affecting the Messaging API and message-related webhooks, where image URLs sometimes fail to work properly. This intermittent issue results in some images not loading and displaying an error message instead (404 not found error). We apologize for any inconvenience this may cause and will provide further updates as soon as they're available.

This incident has been resolved. If you still experiencing this issue, please contact us via the Support Portal.

We experienced an increased number of 500 errors impacting the Message API, which started on Nov 24, 2024 around 10:03 AM (PST). This has been mitigated as of 11:57 AM (PST), on Nov 24. We are monitoring the results. In addition to 500 errors, during the incident, webhooks for newly crated reservations might have been sent without thread IDs. Our engineers have now backfilled the threads for the affected reservations. You can retrieve them using the GET Reservations API. We apologize for the inconvenience caused

This issue has been mitigated as of 12:37 PM (PST). Please retry any failed requests during the incident window. We apologize for the inconvenience.

We are actively investigating an increased number of 500 errors across multiple endpoints, which started today (November 20, 2024) around 11:58 AM (PST). This issue also affects processing requests to Async APIs. Our engineering teams are working to get everything up and running again, and we will update you with the latest information as soon as possible.

This issue has been mitigated as of Wednesday, Nov 13 at 1:50 PM (PST). Please retry any failed requests during this incident window. We apologize for the inconvenience.

We experienced an issue causing an increase in 500 errors across multiple API endpoints. The errors started on Wednesday, Nov 13 at 11:30 AM (PST). This has since been resolved on Wednesday, Nov 13 at 1:50 PM (PST). Please retry any failed requests during this incident window. We apologize for the inconvenience.

On October 28, between 9:30 AM and 3:00 PM (PDT), we experienced an issue with reservation webhook notifications. During this time, guest details, such as last names and phone numbers, were missing from some reservations. To retrieve the missing guest details, please use the GET reservations API. If the issue continues, please contact us through the Support Portal. We apologize for any inconvenience this may have caused.

This incident has been resolved.

All delayed message_added webhooks have been sent out by 3:05PM PST on Saturday, Oct 12. We will continue to monitor this.

We're currently investigating an issue that's causing errors delivering message_added webhooks. A portion of message_added webhooks were not delivered from around 3AM PST on Friday, Oct 11. We've mitigated the issue at around 12PM PST on Saturday, Oct 12, and the delayed webhooks are being sent out. We will continue to monitor this, and send out another update once all the delayed webhooks are sent out.

This issue has been resolved.

We've identified an issue with Readme: some pages aren't loading correctly. Until the issue is fixed, please try hard refreshing your browser to see if that helps load the content correctly. We'll share more updates as soon as we can.

This issue has been mitigated as of 15:44 PM (PST). Please retry any failed requests during the incident window.

We are actively investigating an increased number of 500 errors across multiple endpoints, which started today (August 28, 2024) around 10:30 AM (PDT). This issue also affects processing requests to Async APIs. Our engineering teams are working to get everything up and running again, and we will update you with the latest information as soon as possible.

There was an increase in 500 Errors across multiple endpoints earlier. The errors started on Wednesday, August 28th 10:20 AM PST and were mitigated by Wednesday, August 28th 10:30 AM PST. Please retry any failed requests during the incident window.

We deployed a fix for this issue today, July 29, around noon PDT. If the issue continues, please contact the API Integrations Team through the Support Portal.

We've identified the root cause of the issue and are actively working on a solution. We'll post more updates as soon as we can.

We are investigating an issue where PUT pricing_settings requests are sometimes not clearing standard fees as expected.

This incident has been resolved. If you need additional help, please contact the API Integrations Team through the Support Portal.

A fix has been implemented and we are monitoring the results.

We have identified an issue affecting the sending of reservation and message related webhooks starting on July 18th. We are actively working on it and will post more updates when we have them. This incident does not affect all reservations and messages. If you notice that some of your Hosts' reservations webhooks are missing after accepting make_reservation synchronous check, use the GET Reservations API to retrieve the reservation status.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating an issue that is preventing some partners from creating Support Tickets. For critical issues that require escalation, kindly contact your Airbnb Connectivity Partner Manager. Please see ticket priority guidelines - https://developer.airbnb.com/docs/create-and-manage-support-cases#ticket-priority We are looking into the matter and will update you with the latest information as soon as possible.

There was an increase in 500 Errors across multiple endpoints earlier. The errors started on Monday, June 17th 5:30 PM PDT and were mitigated by Monday, June 17th 6:30 PM PDT. Please retry any failed requests during the incident window.

This incident was resolved on May 9, 2024.

We have implemented a fix for this issue around 8:30 AM PDT today, and we are monitoring the results.

While we continue to investigate this issue, please make sure that the availability for your listings is up-to-date, as booking attempts are still being processed based on the availability reflected on the Airbnb calendar. Please note that this incident is not affecting notifications, and you will receive webhook notifications for reservation requests, confirmation, alteration, and cancellations. We will post more updates as soon as we have them.

We are facing issues where some reservations are being confirmed without Sync Availability Checks for API connected listings. Our engineering teams are investigating the issue and we will update you with the latest information as soon as possible.

This incident was resolved on May 14, 2024.

A fix has been implemented and we are monitoring the results. If you get new reports of this issue, please contact the API Integrations Team via the support portal.

We are currently investigating an issue where the Airbnb calendar incorrectly displays dates as available to guests, even though these dates are already blocked due to existing reservations. As a result, guests can get to the check-out page, but will see an error message that says "These dates are no longer available", and are prompted to select different dates. It's important to note that despite appearing as available, these dates cannot be booked by guests on Airbnb.

This incident has been resolved.

We've identified and fixed an increased number of 500 errors across Messaging API starting 9:30 PM AM PST 18th April. This issue has been mitigated at 4:30 PM PST 22nd April. Please apply any failed requests during the incident.

We are actively investigating an increased number of 500 errors across multiple endpoints. These errors started Friday April 18th, 2024 around 9 PM PDT. Our engineering teams are working to get everything up and running again and we will update you with the latest information as soon as possible.

This incident has been resolved. <recommended steps for partner to take>

Our third-party service, ReadMe, is experiencing an issue which is impacting access to our API Docs and APIX. We will update you with the latest information as soon as possible. We apologize for the inconvenience, and please don't hesitate to contact us if you need further assistance.

This incident has been resolved.

We have deployed a fix for this issue and will now monitor the results. If you are still experiencing this issue, please contact our team via the Support Portal.

We are actively investigating an issue with Host account authorization. When a Host disconnects from an application, their listings are supposed to be disconnected as well. However, we have observed that in some cases, the listings remain API-connected even after the Host account disconnection. This can cause problems when a Host switches from one application to another, as their listings will still be connected to the previous application. We will provide more updates on this issue as soon as possible.

This incident has been resolved.

We have mitigated the issue and re-process all the async API requests. We will continue monitoring the issue.

We are continuing to investigate this issue.

We are currently investigating an issue related to async processing of our pricing and availability APIs. We'll post updates as we have more information.

This incident has been resolved.

A fix has been implemented and we are monitoring the implementation.

We are currently investigating an issue that's causing sporadic errors on a variety of different APIs. The pricing and availability API appears to be primarily impacted, but other endpoints are sporadically affected as well.

This incident has been resolved. Apologies for the inconvenience caused. Thanks for your patience and understanding.

Our third party service, ReadMe, has implemented a fix and we are monitoring the results; you should be able to successfully access the API Docs now. We apologize for this inconvenience!

Our third-party service, ReadMe, is experiencing a wide-spread issue which is impacting access to our API Docs and APIX. We will update you with the latest information as soon as possible. We apologize for the inconvenience, and please don't hesitate to contact us if you need further assistance.

This incident has been resolved. Apologies for the inconvenience caused. Thanks for your patience and understanding.

A fix has been implemented and we are monitoring the results. If you still can't submit cases through the support portal, please let your Connectivity Partner Manager know.

We are currently investigating an issue that prevents partners from creating Support Tickets. For critical issues that require escalation, kindly contact your Airbnb Connectivity Partner Manager. Please see ticket priority guidelines - https://developer.airbnb.com/docs/create-and-manage-support-cases#ticket-priority Our engineering teams are working to get everything up and running again, and we will update you with the latest information as soon as possible.

This incident has been resolved. The effects began around 1:30 PM PST, and were mostly resolved by 2:15 PM PST. There may have been some lingering affects until around 6 PM PST, but at this point we do not expect any further issues.

We are currently investigating an issue that's causing sporadic errors on a variety of different APIs. The Booking Settings API appears to be primarily impacted, but other endpoints are sporadically affected as well.

This incident has been resolved as of March 6th, 2024, 12:08 AM PST. Error rates have returned to normal levels. Please retry any failed requests. We apologize for the inconvenience caused and thank you for your patience and understanding.

We've identified an increased number of 500 errors across multiple endpoints starting today 11:52 AM PST.This issue has been mitigated at 12:08 AM PST. Please apply any failed requests during the incident.

This incident has been resolved.

We've mitigated the issue at 4:10AM PDT and will continue to monitor it.

We are investigating an increased number of 500 errors across multiple availability related endpoints. These errors started on March 01, 2024. Our engineering teams are actively working towards a resolution to restore service fully.

This incident has been resolved. Error rates have returned to normal levels. Please retry any failed requests. We apologize for the inconvenience caused and thank you for your patience and understanding.

The issue has been mitigated at 1:45 PM PDT. Please apply any failed requests during the incident.

We are actively investigating an increased number of 500 errors across multiple endpoints. These errors started today (March 4, 2024) around 12:57 PM PDT. Our engineering teams are working to get everything up and running again and we will update you with the latest information as soon as possible.

This incident has been resolved. Don't hesitate to contact us if you need further assistance.

We recently experienced an incident that affected all reservation-related webhooks between 9:54 AM and 10:44 AM PT on March 4, 2024. During this time, you may have noticed reservations being requested, confirmed, altered, and canceled on your listings, but no corresponding webhooks were received. The issue has been resolved, and we will be sending all the missing webhooks in the upcoming hours. In the meantime, if you need to retrieve reservation information for your listings, you can use the GET reservations API. Please note that this incident only affected reservation-related webhooks. We apologize for the inconvenience, and please don't hesitate to contact us if you need further assistance.

This incident has been resolved.

Our Async Request Processing system had an issue this morning, which resulted in increased delays between the time a request was enqueued and when it was processed, and may have resulted in an elevated processing failure rate. This began around 8:10 AM PST, and was resolved by 9:15 AM PST. We are still actively monitoring, but are not expecting any ongoing issues at this time.

We've identified spikes in errors across multiple endpoints that have occurred over the past day. The two distinct spikes were: - February 5th, 4:10 PM to 4:30 PM (PST) - February 6th, 6:30 AM to 7:30 AM (PST) The issue is now resolved, and we don't expect any ongoing impact.

This incident has been resolved. Please contact us if you still can't see API-connected listings on the Partner Portal.

We are still working on this issue. You may still view listing-related events by filtering by Listing ID on the Partner Portal Events Dashboard. You may also utilise GET requests to view the current snapshots of a listing if required. We apologise for the inconvenience caused.

We are still working on this issue, apologies for the inconvenience.

We are investigating an issue affecting our Diagnostic tools in the Partner Portal that started today Jan 3, 2024 around 12:00PM PST. Currently, you might not see any API-connected listings on the Listings dashboard, and in a listing's overview page, you might see the following message "The listing is not API connected". Please note that no listings were disconnected due to this incident; this issue affects the Partner Portal view only. We are actively working to resolve this issue, and will post more updates as soon as possible.

On Nov 16 and 17, some inquiries and pre-approvals expired prematurely, causing guests to be unable to accept them because Airbnb incorrectly showed these listings as unavailable, even though they were actually available. Additionally, Hosts were experiencing difficulties in creating new pre-approvals during this period. We apologize for the inconvenience that this issue has caused. This issue started on Nov 16 around 12:00 AM PST and was resolved on Nov 17 at 9:10 AM PST, and we expect this to be fully resolved. Please contact us if you are still seeing this issue.

This incident has been resolved.

We have observed a higher number of intermittent 500 errors on the GET Resolutions API. We are actively working on resolving this issue and plan to deploy a fix tomorrow (Nov 9, 2023). Thank you for your understanding and patience as we work to rectify this situation.

This incident has been resolved.

Today (Oct 30, 2023) between 1:00 PM and 3:00 PM PDT we encountered an incident that impacted our webhooks functionality. As a result, some reservations may have been missing webhooks during this time period. The issue has been resolved, and our team is actively monitoring the results to ensure the stability of our systems. If you have noticed any reservations missing webhooks, we recommend using the GET Reservations API to retrieve the details of those reservations. Alternatively, you can contact us with a list of affected reservations, and we will assist you in backfilling the missing information. We apologize for any inconvenience this may have caused and appreciate your understanding.

This incident has been resolved.

There was an increased number of 500 errors on the GET Opportunities API endpoint. We've mitigated the issue and will continue to monitor it. The time window for these errors was between 9:00 PM and 9:50 PM (PDT) today (Oct 3, 2023)

This incident has been resolved.

We're currently investigating an issue that's causing spikes in our delivery timelines for asynchronous webhook notifications. It began around 5PM PST on Friday, September 29, and briefly reoccured on both Saturday and Sunday afternoon. We've mitigated the issue for now, but will continue to monitor this over the next few days.

This incident has been resolved.

There was an issue with the generation of Basic Auth headers for synchronous availability checks and asynchronous webhook notifications between 11:45 AM and 2:00 PM PDT today. This resulted in errors for both availability checks and webhooks. The issue has been resolved, and our team will be monitoring any further errors.