<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>API Access on Tabledoo Blog</title>
    <link>https://tabledoo.com/blog/tags/api-access/</link>
    <description>Recent content in API Access on Tabledoo Blog</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Thu, 01 Oct 2026 09:00:00 +0300</lastBuildDate>
    <atom:link href="https://tabledoo.com/blog/tags/api-access/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>New restaurant tech is coming — how to vet vendors so your reservations and guest flow stay safe</title>
      <link>https://tabledoo.com/blog/posts/new-restaurant-tech-is-coming-how-to-vet-vendors-so-your-reservations-and-guest-flow-stay-safe/</link>
      <pubDate>Thu, 01 Oct 2026 09:00:00 +0300</pubDate>
      <guid>https://tabledoo.com/blog/posts/new-restaurant-tech-is-coming-how-to-vet-vendors-so-your-reservations-and-guest-flow-stay-safe/</guid>
      <description>How to vet vendors and protect bookings: practical advice on reservation system integration, webhooks, API access and guest analytics to keep guest flow safe.</description>
    </item>
  </channel>
</rss>
