--- title: "Requiply 1.2.2: Clients in Main Menu, Automation Updates, More Flexible Date Picker | Requiply" description: "Requiply 1.2.2 promotes Clients to a top-level section with per-user permissions, adds a Send Internal Email workflow action, introduces a configurable booking date picker, a minimum reservation duration, and ships the first public API in beta with token management" canonical_url: "https://requiply.com/blog/1-2-2-release-notes" last_updated: 2026-05-04 locale: en meta: "og:description": "Requiply 1.2.2 promotes Clients to a top-level section with per-user permissions, adds a Send Internal Email workflow action, introduces a configurable booking date picker, a minimum reservation duration, and ships the first public API in beta with token management" "og:title": "Requiply 1.2.2: Clients in Main Menu, Automation Updates, More Flexible Date Picker" "twitter:description": "Requiply 1.2.2 promotes Clients to a top-level section with per-user permissions, adds a Send Internal Email workflow action, introduces a configurable booking date picker, a minimum reservation duration, and ships the first public API in beta with token management" "twitter:title": "Requiply 1.2.2: Clients in Main Menu, Automation Updates, More Flexible Date Picker" --- ![Requiply 1.2.2: Clients in Main Menu, Automation Updates, More Flexible Date Picker](https://requiply.com/.netlify/images?w=10&h=10&fm=webp&q=50&blur=3&url=%2Fblog%2Freleases%2F1-2-2%2Fcover.png) ## What's New in Requiply 1.2.2? This release opens Requiply up — to your team, to your operating model, and to the wider developer ecosystem. **Clients** moves out of Settings and becomes a first-class section governed by per-user permissions. Workflows can now notify your team, not just your customers, with a new **Send Internal Email** action. Booking creation gets a configurable **date picker style** so the reservation flow matches how your business actually rents — by day or by hour. Reservation duration gains a hard **minimum** to protect margins on hourly inventory. And the headline change: Requiply now ships a **public API in beta**, with managed tokens and a stable v1 surface for custom integrations. --- ## 1. Clients — Now a Main Menu Section with Per-User Permissions ![Requiply main navigation showing the new top-level Clients section alongside Inventory, Reservations, and Reports](https://requiply.com/.netlify/images?url=%2Fblog%2Freleases%2F1-2-2%2Fclients-main-menu-en.png) Until now, the Clients (CRM) area lived under Settings and was effectively admin-only. In 1.2.2 it is promoted to a **top-level section** in the main navigation, right where it is used day-to-day — alongside Reservations and Inventory. ### What Changed New main-menu entry: Clients — with the standard sub-pages Manage, Add, Edit, and Import New account permission: Allow Client Management — grant CRM access without giving full admin rights Non-admin users see Clients only when the permission is enabled on their account Existing client data, tags, and segments are unaffected — only access changes ### Where to Configure ![Requiply account permissions panel with the new Allow Client Management toggle next to Inventory, Service, Reservations, Reporting, and Web Site permissions](https://requiply.com/.netlify/images?url=%2Fblog%2Freleases%2F1-2-2%2Fclient-permission-en.png) Open **Settings → Organization Settings → Accounts**, edit a user, and toggle **Allow Client Management**. The permission joins the existing list (`Inventory Manage`, `Service Manage`, `Reservations Manage`, `Reporting Access`, `Web Site Manage`). When the permission is off, the **Clients** item is hidden from the side menu and the `/clients/*` routes redirect to an access-denied page — so the UI matches what the user can actually do. **Practical Use Cases:** - **Front-desk staff** at a bike rental can now own customer records — adding new clients, editing contact details, looking up history — without being granted admin rights to billing or inventory - **Account managers** at an event-equipment company get full CRM access while inventory staff stay out of the customer database - **Dispatchers** at a construction-equipment yard see and edit clients but cannot change pricing or settings --- ## 2. Send Internal Email — Workflows That Notify Your Team ![Requiply workflow editor with the new Send Email to List action, recipient list, and template picker](https://requiply.com/.netlify/images?url=%2Fblog%2Freleases%2F1-2-2%2Finternal-email-action-en.png) Until now, workflow emails always went to the **client**. Many teams need the inverse: an internal heads-up when something important happens — a refund, a no-show, a last-minute booking, a high-value reservation. Version 1.2.2 closes that gap with a new action type. ### The New Action New action type: Send Email to List — internal email notifications Define a list of recipient addresses directly on the workflow (owner, manager, shared inbox, etc.) Uses the same template engine as customer emails — branding and dynamic placeholders work out of the box Add as many recipients as you need — no third-party automation tools required ### Triggers You Can Combine It With All existing workflow triggers are supported — the action plugs into the engine you already use: | Trigger | Example use | | --- | --- | | **Status reached** | Reservation moves to *Cancelled* — alert the manager instantly | | **Payment status reached** | Payment becomes *Refunded* or *Failed* — ping the owner for follow-up | | **Booking created** | A small-inventory rental gets a new public booking — owner is notified the moment it lands | | **Relative time reached** | 24 hours before booking start — operations manager gets a prep reminder | ### Configuration Open **Settings → Workflows → Add Workflow** (or edit an existing one), pick a trigger, then select the **Send Email to List** action. Choose an email template, add one or more recipient addresses, save. **Practical Use Cases:** - **Boutique car rental**: When payment status flips to *Refunded*, automatically email the owner so refunds never go unnoticed - **Photography studio**: When a same-day booking is created from the public site, the studio manager gets an instant heads-up so they can prep the space - **Construction equipment yard**: 24 hours before each booking start, the dispatcher receives a digest so loading is queued the night before - **Event rental**: When a high-value reservation moves to *Cancelled*, sales and operations both get notified so the slot can be re-marketed quickly --- ## 3. Booking Creation Settings — Pick the Date Picker That Matches Your Model ![Requiply Booking Creation settings page with Date Picker Type option showing Range and Single-day choices](https://requiply.com/.netlify/images?url=%2Fblog%2Freleases%2F1-2-2%2Fbooking-creation-settings-en.png) Different rental businesses think about time differently. A car rental cares about *days*. A studio cares about *hours within a day*. The booking flow now adapts to your model. ### What Changed A new settings page, **Booking Creation**, lives under *Settings → Reservations → Booking Creation*. Its main option, **Date Picker Type**, lets you pick how customers (and your staff) select dates and times. ### The Two Picker Styles Range picker — separate start and end (default): customer selects a start date plus time and an end date plus time. Best for multi-day rentals where start and end fall on different calendar days Single-day picker — one date with a time range: customer picks a single date and a time range on that date. Best for same-day services like studios, tours, classes, and hourly rentals ### Where the Setting Applies Public booking page — the picker your customers see when reserving online Internal Add Booking page — what staff use to enter reservations manually Mobile app — will pick up this setting in the next release **Practical Use Cases:** - **Vehicle rental**: Keep the range picker — pickups and drop-offs naturally span multiple days - **Recording studio**: Switch to single-day — clients book a Saturday from 14:00 to 18:00 in one clean step instead of awkwardly entering the same date twice - **Walking tour operator**: Single-day picker fits perfectly — pick a date, choose the 10:00 or 14:00 slot - **Hourly meeting room rental**: Single-day picker keeps the booking flow short and keeps customers from accidentally booking across midnight --- ## 4. Minimum Reservation Duration — Protect Your Margins ![Requiply Reservation Duration settings page with the new Minimum Reservation Duration field shown alongside start and end buffers](https://requiply.com/.netlify/images?url=%2Fblog%2Freleases%2F1-2-2%2Fmin-duration-en.png) The **Reservation Duration** settings page gains a new control: a hard floor on how short a booking can be. ### What Changed New field: Minimum Reservation Duration — set in minutes, hours, or days as you prefer Default: 1 day (1440 minutes) — preserves prior behavior for existing organizations Enforced on the public booking page and internal add-booking flows Picker shows a clear validation message referencing the configured minimum so customers understand why their selection is rejected Works alongside the existing start date and end date buffers on the same page ### Why It Matters Without a minimum, customers were able to book unprofitable 15-minute slots on hourly inventory, or even zero-duration reservations through edge-case flows. Setting a floor protects margins and matches how most rental businesses actually price their offerings. **Practical Use Cases:** - **Recording studio**: Set a 2-hour minimum so the studio is never booked for an unprofitable 30-minute slot that still requires a full setup - **Yacht charter**: Set a 4-hour minimum to match the smallest commercial slot you actually price for - **Co-working day pass**: Set a 1-hour minimum so a stray click cannot create a 5-minute reservation - **Equipment rental**: Keep the 1-day default to mirror the existing pricing structure with no reconfiguration needed --- ## 5. Public API (Beta) — Build Your Own on Top of Requiply The biggest change in 1.2.2: Requiply now ships with a **public, documented HTTP API**. It is in **beta** — endpoints and payloads are stable for production use, but we may add fields and (rarely) introduce versioned changes during this period. ### New Settings Page: API Keys Open **Settings → Organization Settings → API Keys** (admin only). Create, name, rename, and revoke keys at any time. Two key types: Publishable (rq\_pk\_live\_…) for trusted front-end use, and Secret (rq\_sk\_live\_…) for server-to-server calls Tokens are shown once at creation and stored only as a hash plus the last 4 characters thereafter — they cannot be recovered, only rotated Each key shows: name, type, masked value, created date, last used date, and status Revoke any key instantly if a credential leaks — no support ticket required ### Authentication All public endpoints sit under `/api/public/v1/…` and accept a Bearer token: ``` Authorization: Bearer rq_sk_live_xxxxxxxxxxxxxxxx ``` ### Endpoints Available in v1 Organization — GET /org/info for org details, locations, accepted payment methods, and timezone Catalog — GET /inventory/list, /inventory/groups/{id}, /categories/list Availability & pricing — POST /availability/calendar, /availability/items, /pricing/quote Bookings — POST /bookings/create and GET /bookings/{id} Clients — POST /clients/lookup to find an existing client or create one ### Rate Limiting 100 requests per 60-second sliding window, per key. Exceeded calls return `HTTP 429` with a `Retry-After` header. ### What It Unlocks Today Custom booking flows — embed Requiply availability and checkout into your own website, mobile app, or kiosk Operational integrations — sync inventory or bookings with ERPs, accounting tools, dispatch boards, or smart-lock systems Automations — build Zapier/n8n-style workflows that go beyond what our built-in workflow engine covers AI agents and copilots — feed Requiply data into custom assistants that answer customer questions or draft bookings ### Where We're Taking This Next This API is the foundation for our broader developer story. The roadmap from here: MCP server — a Model Context Protocol server so AI agents (Claude, Cursor, custom assistants) can read and act on Requiply data on behalf of operators Official SDKs — typed clients for TypeScript/JavaScript first, then Python Lovable, v0, and other AI-builder integrations — turnkey Requiply blocks so a non-technical owner can describe the booking experience they want and have it generated against our API ### Why This Direction At Requiply, we believe the future of business software is **not** a single closed website builder that everyone has to bend to. It is a stable, well-documented backend that takes responsibility for the hard parts — availability math, payments, scheduling, compliance — and a thriving layer of AI-assisted tools on top, where owners and developers can compose beautiful, custom experiences in hours instead of weeks. Today's release is the first deliberate step toward that world. --- ## Frequently Asked Questions ### Admins keep full access automatically. Non-admins get access only after you grant the new "Allow Client Management" permission on their account — this is intentional, so you can decide who on the team should now own customer records. ### In 1.2.2 the recipient list is defined directly on the workflow (a fixed list of internal addresses). Dynamic recipients pulled from booking or client data are on the roadmap. ### No. Existing bookings keep their stored start and end times unchanged. The picker style only affects how new bookings are created from the public page and internal Add Booking flow. ### The minimum is a hard floor on booking length and is independent of pricing. If your shortest priced slot is 2 hours, set the minimum to 2 hours so customers cannot create reservations below that floor. ### Yes. "Beta" means we may add new fields and, rarely, introduce versioned changes — not that the API is unstable. Endpoints under /api/public/v1/ are intended for production integrations today, and any breaking change would ship under a new version. ### API tokens are created under Settings → Organization Settings → API Keys (admin only). You can create as many as you need — separate keys per integration is the recommended pattern so you can rotate one without affecting the others. ### Secret tokens are stored only as a hash plus the last 4 characters and cannot be recovered. Revoke the lost token from the API Keys page and create a new one — your existing integrations need to be updated with the new value. --- ## What's Next? Version 1.2.2 is about **opening Requiply up** — to your team via permissions, to your business model via flexible booking creation, and to the wider developer ecosystem via the public API. We want to see **what you build on top of the API** and **how internal-email workflows reshape your operations** — that feedback will shape where the platform goes next. Here's what we're continuing to work on in parallel: **MCP server and official SDKs** — typed TypeScript and Python clients, plus a Model Context Protocol server so AI agents can act on Requiply data on behalf of operators. **Custom status flows** — the ability to define your own booking and payment status names, order, and transitions, so the Requiply workflow matches the way your business actually operates. **More workflow triggers and actions** — we're expanding the automation engine: more triggers, branching conditions, and a wider set of actions, so you can automate almost any routine in your rental process. **Additional notification channels** — email is just the start. We're planning SMS, WhatsApp, and other channels so you can reach clients the way they actually respond. **Custom domain management** — connect your own domain and send emails from your own address, so every automated message lands in the client's inbox with your brand. --- **Have questions or suggestions?** Write to us at `info@requiply.com` — we're especially interested in hearing what you build with the new public API and which integrations you'd like us to prioritize. **Tags** - Requiply version - requiply - clients permission - client management - workflow actions - internal email - booking creation - date picker - minimum reservation duration - public API - API tokens - rental software - booking management - developer tools ## Sitemap See the full [sitemap](/sitemap.md) for all pages.