Integration
Connect Ventrata to ip-api
When Updated Booking fires in Ventrata, your agent runs Get IP geolocation in ip-api. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Ventrata and ip-api to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Ventrata can start in ip-api
When Updated Booking in Ventrata
then Get IP geolocation in ip-api
When Updated Booking in Ventrata
then Get IP geolocations (batch) in ip-api
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Ventrata and ip-api
Triggers and actions 1 trigger ยท 13 actions
Trigger
Updated BookingTriggers when any booking is created, updated, cancelled, or redeemed, including changes to customer details, products, options, quantities, or status.
Action
Add bookingReserves availability by creating an ON_HOLD booking. Confirm it afterwards with Confirm booking.
Action
Confirm booking/bookings/{uuid}/confirm - confirm an on-hold booking with contact details (OCTO Core).
Action
Delete booking/bookings/{uuid} - cancel a booking with optional reason (OCTO Core).
Action
Find availability/availability - search availability for a product/option over a date range or specific dates (OCTO Core).
Action
Find availability calendar/availability/calendar - daily availability summary for a product/option over a date range (OCTO Core).
Action
Find BookingFind bookings by reference, date, contact details or other filters. At least one primary filter is required.
Action
Get booking/bookings/{uuid} - retrieve a booking by UUID (OCTO Core).
Action
Get product/products/{id} - retrieve one product with its options and units (OCTO Core).
Action
Get supplierReturns the supplier the connected API key belongs to (name, reference, website, contact details).
Action
List products/products - list all bookable products for the supplier (OCTO Core).
Action
Update booking/bookings/{uuid} - amend an existing booking (date/time, units, contact) (OCTO Core).
Action
Get IP geolocationLook up geolocation, ISP, and network details for an IP address or domain.
Action
Get IP geolocations (batch)Look up geolocation details for up to 100 IP addresses or domains in a single request.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Ventrata
Ventrata to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Ventrata to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
Ventrata to WixThe Wix website builder gives businesses of any size the tools to create, manage and grow a fully integrated...
Ventrata to LinkedInLinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...
Ventrata to FacebookFacebook is a social media and advertising platform used by individuals and businesses to connect, share...
Ventrata to AnthropicAnthropic builds Claude, a family of large language models.
More into ip-api
Google Calendar to ip-apiGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Booqable to ip-apiBooqable is cloud-based rental software to manage your business and accept online bookings.
MOCO to ip-apiMOCO (MObile COmpany) is a lean cloud software made for small medium-sized agency and service businesses.
HubSpot to ip-apiHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to ip-apiSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to ip-apiSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Questions
Ventrata and ip-api, answered
What can start an automation from Ventrata?
Any of Ventrata's 1 trigger in the catalog, including Updated Booking. Describe the moment in plain language and your agent picks the right one.
What can your agent do in ip-api when something happens in Ventrata?
Any of ip-api's 2 actions, including Get IP geolocation and Get IP geolocations (batch). Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from ip-api to Ventrata?
ip-api has no triggers in the catalog today, so automations start in Ventrata. If you need the other direction, ask: your agent reads ip-api's API documentation and adds it.
Do I have to build a connector for Ventrata or ip-api?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.