Custom Recras integration development
Appfront builds integrations with Recras, the software for recreation businesses such as climbing parks, event venues, bike rental and indoor attractions. Recras offers standard integrations with, among others, payment services, accounting packages and websites, and an API for those who want more. We use that API and webhooks to connect Recras to your own website or app, your point of sale, CRM or dashboard, so that bookings and data are consistent everywhere and processes start automatically when a booking is made.
What is a Recras integration?
Recras is an online system for (day) recreation businesses, bringing bookings, staff, administration and communication together in one place. It has integrations with, among others, payment services, accounting packages and websites. For larger businesses with their own requirements, Recras offers an API, which lets booking functions be used in a custom website or app and lets Recras be connected to other systems. That is the integration we build.
Without a custom integration, gaps remain. A custom app or website shows packages that don't match availability in Recras. Bookings are keyed in by hand into a till or CRM. A group that books receives no automatic confirmation in your own app's branding. And management wants occupancy and revenue per package, alongside other sources, in a single dashboard.
We build custom software because the integration has to fit your business: which arrangements and activities you sell, through which channels bookings come in, which point-of-sale and CRM systems you use, what should happen when a booking is made, and which figures you want to see. We look at which data the Recras API offers and which webhooks are available in the first step.
Booking where the guest is
Packages and availability from Recras in your own website or app, with booking and payment, without the data drifting apart.
Data the same everywhere
Bookings sent to your till, CRM and accounting, so nobody re-enters them and every system shows the same figures.
Processes that start automatically
A webhook fires on a new booking or enquiry to start a confirmation, a task or a message in another system.
How we build your Recras integration
We start with your channels: where bookings come in, which systems you use alongside Recras, and where data is currently re-typed by hand.
Your packages, channels, systems alongside Recras, and what should happen when a booking is made.
The Recras API for availability and bookings, and webhooks for events, feeding your own systems.
Testing with real packages and bookings, error monitoring, and a log for each message.
Phased go-live per channel, and maintenance when Recras or your systems change.
What a Recras integration does in practice
The components below come up in almost every Recras integration. Which ones you need depends on your channels and systems.
Arrangements
Arrangements, activities and prices from Recras in your website or app.
Availability
Live availability by day and time slot, so only bookable slots are shown.
Bookings
Booking and payment in your own environment, with the booking held in Recras.
Webhooks
A new booking or enquiry that starts a process in another system.
Till and CRM
Bookings and guests sent to your till, CRM and marketing systems.
Dashboard
Occupancy and revenue per arrangement sent to your own dashboard.
Who we build Recras integrations for
The integration is designed for recreation businesses that use Recras alongside their own systems.
Climbing parks and attractions
Plenty of walk-in visitors and groups. Availability in your own app is the core.
Event venues
Arrangements for businesses and groups. The integration with CRM matters most.
Hire companies
Bikes, boats or equipment by time slot. Bookings and the till are what's needed.
Leisure businesses with multiple locations
One system across several sites. The dashboard is the core.
Technology and integrations
This page is about integrations with Recras. For apps in the leisure sector, see our page on a leisure app, for holiday parks and campsites our page on software for parks and leisure, and for booking in general our page on booking software. You can read about our approach at building software.
Why Appfront for your Recras integration?
A guest who books something in your app that is no longer available leaves disappointed. We build around preventing that: availability that is accurate, data that matches everywhere, and processes that run on their own.
No double bookings
Availability comes from Recras. What can be booked in your app is genuinely free.
No manual re-keying
Bookings flow automatically to the till, CRM and accounting.
Figures in one place
Occupancy and revenue from Recras alongside your other sources in a single dashboard.
Security and privacy in a Recras integration
The integration processes guest, booking and payment data. API keys are stored encrypted and used only by the integration, with only the permissions it needs.
The integration runs in a European data centre, with encrypted storage, daily back-ups and a log of every message.
Frequently asked questions about a Recras integration
Questions leisure businesses ask before getting started.
Recras is an online system for (day) leisure businesses, bringing bookings, staff, administration and communication together in one place. It is used by climbing parks, event venues, bike hire and indoor attractions, among others.
Yes, with payment services, accounting packages and websites, among others. These are often enough. A custom integration is needed for your own app, a till or CRM that is not on the list, or processes that need to start when a booking is made.
Through the Recras API and webhooks, which send a signal when a booking or enquiry is made. We look at which data is available in the first step.
Yes. Arrangements, availability and booking come from Recras and are shown in your own app or website, in your own design.
Whatever you need: a confirmation in your own style, a task for the team, a message to a partner, or the booking in your CRM. A webhook starts the process.
The integration reports it and records what went wrong. The message is retried or set aside for manual review.
For recreation businesses with their own app, multiple systems alongside Recras, or processes that the standard integrations don't cover. With just a website and an accounting package, the standard options are often enough.
Connect Recras to your own app and systems?
Tell us where guests book, which systems you use alongside Recras and what should happen when a booking is made. We'll show you what the integration would look like.