Testing a scheduling flow usually takes a few real Google and Outlook accounts and a person to click Accept, which makes the decline and counter paths hard to run more than once or twice. Reclario is an auto-RSVP sandbox. Send a real ICS invite (METHOD:REQUEST) to any address on your private domain and the address tag picks the response. The reply goes back to the organizer from the attendee's address, the same way a person's reply would.
If your product can send a calendar invite by email, you can test it here. Addresses need no setup.
A private catch-all domain for your team at $49/mo per domain, with unlimited addresses.
yourteam.reclar.ioSend it from Google Calendar, Outlook, your ATS or raw ICS in code. The tag on the address picks the response.
interview+accept@yourteam.reclar.ioThe invite shows up as an RSVP card with When, Where and Organizer, and a real iTIP REPLY goes to your organizer.
REPLY: accepted+accept sends an acceptance back to the organizer, so your confirmation flow runs all the way through.
+decline covers what your product does when the invitee says no. Most teams never test it.
+maybe replies tentative. Use it to check how your scheduling UI shows someone who might come.
+delay5 holds the reply for five minutes. That's long enough to see what your UI shows while an invite is pending and whether your reminder logic fires.
Tag the address +counter (or +counter30 for a 30-minute shift) and the reply proposes a new time, which is how you test reschedule and negotiation handling.
Each response is a real iTIP REPLY email to the organizer. Google, Outlook and your own product parse it the same way they would a reply from a person.
Google Calendar, Outlook, your ATS, a scheduling product or ICS generated in code: if it emails a METHOD:REQUEST invite, Reclario can answer it. Your domain is catch-all, so every test case can have its own attendee. A hundred test candidates can each answer differently, and none of them is a real account.
Reclario is a test harness, not a calendar server. It responds to invites (METHOD:REQUEST) sent to your addresses. It doesn't host calendars, book rooms or create events of its own. When you want to drive a specific path by hand, answer the invite yourself from the inbox. For automated runs, API keys and webhooks let CI provision addresses and assert on the responses.
METHOD:REQUEST. That is what Google Calendar, Outlook and Exchange, ATS and scheduling products, and ICS generated from code all send.+ decides the response. interview+accept@yourteam.reclar.io accepts, +decline declines, +maybe answers tentative, and +delay5 waits five minutes before replying, the way a person might. Tags combine, so interview+decline+delay5@ declines after five minutes. You never create the address first; it works the first time an invite is sent to it.+counter and Reclario proposes the same meeting an hour later; +counter30 moves it 30 minutes. That's how you test a reschedule or a negotiation as well as a straight accept.RSVPs go out from private domains only (the free public sandbox at public.reclar.io receives mail but never sends any). A private catch-all domain is $49/mo per domain after a 14-day free trial (card required).
Start free See pricing