Flavours API Documentation
Flavours API Documentation
  • Readme
  • Developer Guide
  • Authorization
  • Includables
  • Pagination
  • Sorting
  • Retrieve Market Information
  • Retrieve Branch Information
  • Me
    • Overview
    • Detail
      GET
  • Branches
    • Overview
    • List
      GET
    • Detail
      GET
    • Create
      POST
    • Update
      POST
    • Delete
      DELETE
  • Orders
    • Overview
    • List
      GET
    • Detail
      GET
    • Create
      POST
    • Calculate
      POST
    • Checkout
      POST
    • Update
      POST
  • Customers
    • Overview
    • List
      GET
    • Detail
      GET
    • Create
      POST
    • Update
      POST
  • Products
    • Overview
    • List
    • Detail
    • Create
    • Update
    • Delete
  • Product Categories
    • Overview
    • List
    • Detail
  • Discounts
    • Overview
    • List
    • Detail
    • Verify
  • Payment Methods
    • Overview
    • List
    • Detail
  • Table
    • Overview
    • List
    • Detail
    • Create
    • Update
    • Delete
  • Printer
  • Webhook
    • Orders Webhooks
      • Webhook Events
      • Payload
    • Product Webhooks
      • Webhook Events
      • Payload
    • Loyalty Webhooks
      • Promotional Coupon
    • Customers Webhooks
      • Webhook Events
      • Payload
    • Error Webhook
      • Stay Alert to Connectivity Issues
    • Third-Party
      • Ballurh
        • Install Ballurh
      • Loyapro
        • Loyalty
          • Check Reward
          • Redeem Reward
      • Bonat
        • Check Reward
        • Redeem Reward
      • Fai
        • Register Entity

Developer Guide

Developer Guide: Environments#

Flavours provides dedicated environments for each stage of development, ensuring seamless integration and testing without disruptions:

Environment Overview#

Development Environment: A sandbox environment where new features are built, tested, and refined before moving to production.
Production Environment: The live platform for processing real-time transactions at active restaurants.

Development Environment#

Purpose: Provides a safe space for developers to build, experiment, and test new features without affecting live data.
Key Features:
Supports API development, debugging, and iteration.
Isolated from the production environment to prevent unintended disruptions.

Production Environment#

Purpose: Live transactions and real-world usage.
Key Features:
Handles actual data and transactions for active restaurants.
Isolated from the production environment to prevent unintended disruptions.
By understanding these environments and their distinct purposes, you'll ensure a smooth integration process and successful deployment of your API integration.
Modified at 2025-02-16 09:31:55
Previous
Readme
Next
Authorization
Built with