Docs
Visit Flip.toManage your platform
  • About Flip.to Docs
  • Get Started
    • Quickstart
  • Platform
    • Discovery
      • Launchpad
      • Day-to-day
      • Experiences
        • Libraries and Management
        • Flip.to 🀝 OccasionGenius
      • Planner audiences
    • Advocacy
      • First campaign
      • Curation
        • Getting the most out of Curation
      • Stories
      • Promoting a campaign
      • Top storytellers
    • Collaboratives
      • Collaborative Insights
      • Campaign Tracking
      • Brand Resources
    • Mission Control
      • Branding
      • Point person
      • Seasonal photos
      • Booking engine URL
      • Custom domains
      • Languages
      • Team
  • Integrations
    • Websites
      • Set up your website
      • Cross-domain tracking
      • Member tracking
      • Website markup
      • Feature previews
    • Booking Engines
      • Set up your booking engine
      • Vendors
        • SynXis
        • iHotelier
        • RevRaise by AZDS
        • RezTrip
        • SiteMinder
        • Newbook
        • Cloudbeds
        • Campspot
    • Analytics
      • Signals & subscriptions
      • Consent management
    • CRMs
      • Zapier
        • Using Zapier with Mailchimp
      • Revinate
      • Salesforce
      • SFTP
    • Email
      • Confirmation email
      • Pre-arrival email
      • Post-stay email
      • Cancellation email
    • Marketing
      • Google Ads
      • Microsoft Advertising
      • Meta Ads
      • TikTok Ads
  • API
    • Introduction
    • Reference
      • Platform API
      • Collaborative API
  • Support
    • Customer Success
    • Policies
Powered by GitBook
On this page
  1. API

Introduction

The Flip.to API is organized around REST. It is a standards-based API that has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.

API Authorization

All requests must be authorized with an API Key that is available in your Flip.to account. It should be sent using basic authentication as the “username” with no password. For example, if the key were “nevergoingtogiveyouup:”, the requests would need a header like this in base64:

Authorization: Basic bmV2ZXJnb2luZ3RvZ2l2ZXlvdXVwOg==
PreviousTikTok AdsNextReference

Last updated 1 year ago