Access Development is a loyalty and discount network provider for North American membership organizations, associations and employers, supplying white-label member benefit, rewards and employee discount programs. For operators, it brings closed member audiences in the United States and Canada: association members, employees and loyalty program participants browsing a catalog of more than a million merchant offers across dining, retail, travel and entertainment, a channel outside open consumer search.

Connecting Access Development to Ventrata syncs your availability and prices and delivers bookings, changes and cancellations with tickets issued automatically.

To learn more about partnering with Access Development, visit accessdevelopment.com.

Primary website	accessdevelopment.com
Tags	B2B Marketplace · Deals & Corporate Benefits
Destination markets	🇨🇦 Canada · 🇺🇸 US
Source markets	🌎 Global
Specialties	Closed member benefit and employee discount programs
Connection features	Availability Sync · Pricing Sync · Bookings Sync
Ventrata Booked GMV (last 12 months)	US$10k+
Developed by	Access Development (using Ventrata's OCTO API)

This reseller connection lets you sell your products through Access Development without managing availability, pricing and bookings by hand. Features of this connection include:

Availability Sync – Access Development checks your live availability in Ventrata.
Pricing Sync – Access Development gets your prices from your reseller pricing in Ventrata.
Bookings Sync – bookings, updates and cancellations from Access Development are created in Ventrata instantly, and customers get Ventrata tickets.

Creating the Access Development Connection

🔐 Required Role Permissions: See Connections, Modify Connections, See Connection Key

Before you begin:

You must have a commercial agreement with Access Development for them to sell your products. To inquire about partnering with them, contact them via accessdevelopment.com.
You must have Access Development created as a Reseller in Ventrata with their pricing (retail, wholesale/commission) defined correctly. Note that this API connection requires that the reseller is set to the "Bill to my account" settlement method.

In Ventrata Dashboard, go to Connections → Connections, click + New Connection, and select Access Development from the list of partners.
Select Access Development Reseller from the list of your resellers (must be created before creating a connection). The connection will inherit the reseller's configuration like pricing, allowed destinations, products, etc.
(Optional) You can also set the connection Name of your choosing, which may be helpful if you plan to have multiple Access Development connections and would like to differentiate between them more easily in the future.
Press the Create Octo Connection button.

📗 TIP

If needed, you can also allow or disallow products or destinations on the connection level, in addition to what you have configured on the reseller.

Mapping Products to Access Development

Securely share the OCTO API key shown on the connection you've created with your Access Development contact and ask them to map your products using Ventrata's OCTO API, with pricing (octo/pricing) enabled. Typically, it takes no longer than a few business days for the Access Development team to complete this.

Your Ventrata configuration is complete. You do not need to take any further steps.

📗 TIP

Access Development can access all products enabled on the connection, but you can also provide the Product and Option IDs from the connection page when contacting them to specify what to map.

Managing the Access Development Connection

Allow or disallow products: limit which destinations, products and options Access Development can access. See how to allow or disallow products.
Rename the connection to tell several Access Development connections apart.

Connection Features Detailed

This section is for anyone who wants to know exactly how the Access Development connection works: which Ventrata OCTO API calls Access Development makes, when it makes them, and what that means for you. Each call links to Ventrata's API documentation.

In short: Access Development pulls everything it needs from Ventrata. It reads your products, checks your availability (and your prices, when it asks for them), and sends bookings and cancellations. Ventrata doesn't push changes to Access Development, so anything you change in Ventrata reaches Access Development the next time it checks.

Timings are typical for Access Development and rounded, and they can change if Access Development changes how it syncs.

Product Mapping	❌	You can't map products from Ventrata. Access Development maps them on its side, through your account manager or Access Development's portal. This works as follows: Get Products (`GET /products`) – when Access Development sets up your connection, and whenever it refreshes its listings, it reads every product enabled on the connection, with its options and units (ticket types such as Adult or Child). Get Product (`GET /products/{productId}`) – Access Development re-reads a single product to pick up changes to its options, units, booking cutoffs and settings. Mapping on Access Development's side – Access Development links each Ventrata option and unit to its own listing and ticket types. Your Access Development account manager does this for you, or you do it in Access Development's own portal if Access Development offers one. You only share the connection's API key. Typically with Access Development: It re-reads each product about every 2 hours. What this means for you: Access Development can only sell what it has mapped. When you add a product, option or unit in Ventrata, Access Development may see it on its next refresh, but it won't sell it until it's mapped. So tell your Access Development account manager whenever you add one.
Content Sync	❌	Access Development doesn't read your product content from Ventrata. Access Development uses the descriptions, images and other content set up on its own side, so update your content with Access Development directly.
Availability Sync	✅	Access Development checks your live availability in Ventrata. Ventrata doesn't push availability changes to Access Development. This works as follows: Availability Check (`POST /availability`) – Access Development sends a product, an option and a date or date range. Ventrata answers with each bookable day or time slot, its status (`AVAILABLE`, `LIMITED`, `SOLD_OUT`, `CLOSED` or `FREESALE`), the remaining vacancies, the booking cutoff and an `availabilityId`, which Access Development needs to book that slot. Availability Calendar (`POST /availability/calendar`) – returns one summary per day instead of every time slot, typically to show which dates are open in a date picker. Check at booking – when a customer books, Ventrata checks capacity again before it creates the booking, so Access Development can't overbook a slot that has just sold out, even if its stored availability is slightly out of date. Typically with Access Development: Availability Check: Access Development checks your products throughout the day, usually starting 20 days ahead and covering a single day per request, looks up to about 5 months ahead and re-checks the same product and dates about every 8 hours. Availability Calendar: Access Development checks your products throughout the day, usually starting today and covering 51 days per request, looks up to about 9 months ahead and re-checks the same product and dates about every 5 hours. Checks are busiest between 15:00 and 21:00 UTC, which suggests most checks are live, as customers browse Access Development. What this means for you: when you close a date, change capacity or sell out in Ventrata, Access Development shows it after its next check. For dates it checks regularly, that's within about 8 hours. Dates further ahead are usually checked less often.
Pricing Sync	✅ / ❌	Your prices come back with availability only when Access Development asks for them, and Access Development doesn't always do so. This works as follows: `octo/pricing` capability – Access Development asks for prices by adding `octo/pricing` to the `Octo-Capabilities` header of its requests. Without it, Ventrata sends availability with no prices at all. Availability Check (`POST /availability`) – with pricing on, each day or time slot comes back with your price per unit (ticket type): the retail price the customer pays and the net price you invoice Access Development, both from the reseller's pricing in Ventrata (retail and wholesale/commission). Group prices – when Access Development also sends how many people of each unit type are booking, Ventrata prices that exact group. This matters for Booking Size fares and other group pricing. Booking Reservation (`POST /bookings`) and Booking Confirmation (`POST /bookings/{uuid}/confirm`) – the booking comes back with its final retail and net price, so the booking in Ventrata always records the price it was sold at. Typically with Access Development: Access Development requests `octo/pricing` on only part of its availability checks, so not every listing may use your Ventrata prices. Access Development sends the number of people per unit type, so group prices are calculated for the actual booking. ‼️ IMPORTANT – Ask for pricing to be enabled. When you ask Access Development to map your products, ask them to enable pricing (`octo/pricing`) as well, or switch it on yourself if you map in Access Development's portal. Otherwise it may be off, and Access Development won't receive your Ventrata prices.
Promotions Sync	❌	Your Ventrata promotions don't apply on Access Development. Prices on Access Development don't include promotions you create in Ventrata. Set up any promotions with Access Development directly.
Bookings Sync	✅	Bookings and cancellations made on Access Development are created in Ventrata instantly, and customers get Ventrata tickets. This works as follows: Hold: Booking Reservation (`POST /bookings`) – when a customer starts checkout on Access Development, Access Development sends the product, option, chosen slot (`availabilityId`) and one unit item per person. Ventrata checks capacity again and creates an `ON_HOLD` booking, which holds the places while the customer pays. If there's no longer room, Ventrata rejects the hold. Confirm: Booking Confirmation (`POST /bookings/{uuid}/confirm`) – once payment goes through, Access Development confirms the hold, with its own booking reference and the customer's contact details. The booking becomes `CONFIRMED` in Ventrata, and Ventrata sends back your booking reference and the tickets (one per person) or a voucher (one per booking), depending on how your product is set up, each with a QR code and a PDF link. Access Development gives these to the customer, who shows them at your entrance like any Ventrata ticket. Expire: if the customer doesn't finish paying, Access Development never confirms, and the hold expires on its own and frees the places. Cancel: Booking Cancellation (`POST /bookings/{uuid}/cancel`) – when a customer cancels on Access Development, Access Development cancels the booking in Ventrata. Ventrata accepts this only if the booking can still be cancelled and the option's cancellation cutoff hasn't passed. Otherwise it rejects the request, and Access Development has to contact you. Change: Access Development doesn't use Booking Update (`PATCH /bookings/{uuid}`), so a change most likely reaches Ventrata as a cancellation plus a new booking. Typically with Access Development: Access Development doesn't set a hold time, so the default hold time applies. A typical Access Development booking is for about 3 people. Access Development also checks the bookings it has made, with Get Booking (`GET /bookings/{uuid}`) about once a day, for example to reconcile its records. ‼️ IMPORTANT – Bookings sync one way, from Access Development to Ventrata. If you cancel, change or rebook a booking from Access Development in Ventrata, for example in the Dashboard, Access Development isn't notified. Contact Access Development so the booking is cancelled or changed on their side too, or ask the customer to cancel through Access Development.
Pickups/Dropoff Sync	❌	Access Development doesn't send pickup or drop-off details with its bookings. If your products include pickups, check with Access Development how it collects pickup details, or arrange them with the customer.
Custom Questions Sync	❌	Access Development doesn't send answers to your booking questions. If you rely on booking questions, for example names or dietary needs, check with Access Development how it collects that information.
Extras Sync	❌	Extras and add-ons can't be booked through Access Development. Customers can only book your main products and options on Access Development. Sell extras separately, for example on arrival.
Redemption Sync	❌	Redemptions aren't reported to Access Development. Ventrata doesn't notify Access Development when a ticket is scanned or redeemed. Access Development only sees a redemption if it reads the booking back from Ventrata.
Pass Walkup Scanning Sync	❌	Access Development pass holders can't be scanned at your entrance without a booking. Customers from Access Development need a booking made through Access Development before they visit.
Gift Card Sync	❌	Ventrata gift cards can't be sold or redeemed through Access Development. Gift cards bought in Ventrata can't be used on Access Development, and Access Development can't sell Ventrata gift cards.

✅ supported · ✅ / ❌ limited · ❌ not supported

Good to know: limits and details of the Access Development connection

Delays: availability and prices reach Access Development only when it checks, so there's always a short delay after you change something in Ventrata.
Cancellation cutoff: Access Development can cancel over the API only before your option's cancellation cutoff. Later cancellations have to be agreed with you.
What Access Development can see: only the destinations, products and options allowed on the reseller and the connection, and enabled for sale on the Direct API source. See how to allow or disallow products.
Tickets: Access Development issues the Ventrata tickets or voucher it gets on confirmation, so your usual scanning and redemption work as normal.
Test bookings: Access Development can send test bookings while it sets up the connection. Test bookings don't use your availability and aren't invoiced.

FAQs

No products are displayed on the connection page.

Verify which destinations, products, and options are allowed on your reseller and connection. Next, confirm that your products and options are enabled for sale on the Direct API source. If the issue persists, contact our Technical Support.

My Ventrata products use Booking Size fares, and pricing isn't working correctly on Access Development.

After every fare change, update the product mapping to ensure the partner tier counts are synced with Ventrata. Ensure the fare is enabled for sale over Direct API.

📚 More about Ventrata connections

Partner Information

Access VG, LLC

1012 West Beardsley Place, Salt Lake City, Utah 84119

United States

accessdevelopment.com

Ventrata Partner ID: 5249c29a-f760-4659-8c34-608d0fdcf697

Access Development: Reseller Connection