Integration

Yoplanning integration

Yoplanning is booking and planning software for activity providers such as ski schools, guides and outdoor centres. Read teams, the online catalogue (products, availabilities with prices, sellable options and resources), categories, orders and payments; place, hold, confirm, extend and cancel orders, record payments and apply promo codes; manage clients, staff members, staff unavailabilities, resources, sessions and session groups; read attendances, staff fees, cart rules, booking engines, providers and resellers. Clients, staff members, orders, payments and session participants hold personal data. Placing a confirmed order emails the booking to the client. Not exposed: other users' login tokens, ticket PDFs and ticket validation, team creation and settings, product template writes, session group updates and webhook subscriptions (Yoplanning sets those up through its support). Authentication is the API token from your Yoplanning settings (section Advanced), sent as Authorization: Token <token>.

Connect Yoplanning How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Yoplanning.Built from the 58 Yoplanning tools below, on the connection you add once.

What you can do with Yoplanning

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Payment, 5 operations

create_order_paymentCreate order paymentPOSTRecords a payment a client made on an order, fully or partially (online or at the office). amount and client are required. Refused on an order on hold: confirm it first.
get_order_paymentGet order paymentGETReturns one payment of an order: amount, paying client, source, method, card brand, status (done, pending, failed, cancelled), creation date, operator and external reference.
get_team_paymentGet team paymentGETReturns one payment of the team (from any order): amount, paying client, source, method, card brand, status, creation date, operator and external reference.
list_order_paymentsList order paymentsGETLists the payments recorded on one order: amount, paying client, source (office, online, payment_link), method, card brand, status and date. Paginated.
list_team_paymentsList team paymentsGETLists all the team's payments across orders, filterable by order, client, amount, card brand, operator, creation date, source, method or status. Paginated.

Client, 4 operations

create_clientCreate clientPOSTCreates a client (a person who books activities) in the team. first_name and last_name are required; company and country are required for a professional client. Returns the client with its new id.
get_clientGet clientGETReturns one client (personal data): name, email, phone, birth date, sex, language, company, note, address, custom field answers (extra_data), legal data and marketing consents.
list_clientsList clientsGETLists the team's clients (personal data: name, email, phone, birth date, address), filterable by name, email, phone, address, birth date or last update. Paginated with limit and offset.
update_clientUpdate clientPUTUpdates a client. Yoplanning recommends reading it with get_client, changing the fields and sending the whole object back: a partial update may be rejected or lose data.

Member, 4 operations

create_memberCreate memberPOSTAdds a staff member to the team. This sends the person an invitation email to log in to Yoplanning unless send_invitation is 0. person needs first_name, last_name and email.
get_memberGet memberGETReturns one staff member's person details: id, first and last name, birth date, phone number, language and email (personal data).
list_membersList membersGETLists the team's staff members (instructors, guides, teachers) with name, birth date, phone, language and email (personal data). Anonymous staff are not returned. Paginated.
update_memberUpdate memberPUTUpdates a staff member's person details (name, birth date, phone number, language). The email cannot be changed and is left as it is.

Order, 4 operations

create_orderCreate orderPOSTPlaces an order (booking). CONFIRMED (default) is written whatever the availability, emails the booking to the client and notifies the staff. ON_HOLD holds the places for expiration_minutes, with no payment and no email until confirm_order.
delete_orderDelete orderDELETEDeletes an order by id.
get_orderGet orderGETReturns one order: items (session group, voucher or resource sold, client, price), payments, main client (personal data), currency, reference, source, booking status and its expiry, confirmation or cancellation dates.
list_ordersList ordersGETLists the team's orders (items, payments, main client, booking status), with clients' personal data. Only CONFIRMED orders unless booking_status says otherwise. Send creation_date__gt and creation_date__lt, or last_update__gt to sync.

Resource, 4 operations

create_resourceCreate resourcePOSTCreates a resource (an option allocated to participants of a session, which can also be sold). price is required; stock null means unlimited.
get_resourceGet resourceGETReturns one resource: internal name, label, price, taxes, stock, per-session pricing, staff bonus, reseller fee, type and translated labels and descriptions.
list_resourcesList resourcesGETLists the team's resources (equipment, insurance, questions, pickups allocated or sold with sessions) with price, stock, taxes and translated labels; filter by label, name or price.
update_resourceUpdate resourcePUTUpdates a resource. Yoplanning recommends reading it with get_resource, changing the fields and sending the whole object back. price is required.

Unavailability, 4 operations

create_unavailabilityCreate unavailabilityPOSTMarks a staff member unavailable for a period, so they cannot be assigned to sessions. partial true: for this team only; false: for all their teams.
get_unavailabilityGet unavailabilityGETReturns one unavailability: start and end, staff member id, reason, external reference and whether it applies to this team only (partial).
list_unavailabilitiesList unavailabilitiesGETLists periods when staff are unavailable. Send start_date__lt (end of your window) with end_date__gt (its start) to get those overlapping it; filter by staff. Paginated.
update_unavailabilityUpdate unavailabilityPUTUpdates a staff unavailability: dates, reason, partial. start_date, end_date and teacher_id are required.

Session group, 3 operations

create_session_groupCreate session groupPOSTSchedules activities: creates a session group (sessions sold together, such as a 6-day ski course; one session also needs a group). Each session needs start_date and end_date on the same day.
get_session_groupGet session groupGETReturns one session group: price, its sessions (dates, staff, product, participants), main_group_id (set when it is a sub group) and team.
list_my_session_groupsList my session groupsGETLists the session groups assigned to the user who owns the API token, as a teacher (staff), with their sessions and participants. Paginated with limit and offset.

Attendance, 2 operations

get_attendanceGet attendanceGETReturns one attendance: start and end date, the member (teacher) id and the staff status (id and name).
list_attendancesList attendancesGETLists the work periods (attendances) of the team's members, each with its staff status; filter by teacher, staff status name or start date. Paginated.

Booking engine, 2 operations

list_booking_enginesList booking enginesGETLists the team's booking engines (online shops): name, whether it is the main one used for office sales, voucher-only and shop-only flags, domain and creation date.
list_provider_booking_enginesList provider booking enginesGETLists the booking engines of one of the team's providers. Restricted to some teams: Yoplanning support grants access.

Cart rule, 2 operations

get_cart_ruleGet cart ruleGETReturns one cart rule: validity dates, promotion (amount or percentage), required quantity, condition and effect (product, product tag or session tag). Orders created through this API do not apply cart rules.
list_cart_rulesList cart rulesGETLists the team's cart rules (automatic 'buy X, get a discount on Y' promotions applied by the booking engine cart), ordered by name; filter by name or dates. Paginated.

Category, 2 operations

get_categoryGet categoryGETReturns one activity category by its numeric id, with its sub categories and their names in each language.
list_categoriesList categoriesGETLists every Yoplanning activity category (such as Water sports) with its sub categories (such as Aquabike) and their translated names. Sub category ids filter list_online_products. Paginated.

Online product, 2 operations

get_online_productGet online productGETReturns one product sold online: titles and descriptions, duration, place, category, participant settings and indicative prices, as in list_online_products.
list_online_productsList online productsGETLists the products sold online (the booking catalogue): titles, descriptions, duration, place, category and indicative prices. Filter by availability dates, sub category or team; lang translates texts.

Online resource, 2 operations

get_online_resourceGet online resourceGETReturns one resource sold online: public label, internal name, type, price, taxes, whether priced per session, and stock.
list_online_resourcesList online resourcesGETLists the resources sold online (equipment, insurance, questions, pickups) with label, type, price, taxes and stock. A reseller also gets its providers' resources; filter with team_id.

Product, 2 operations

get_productGet productGETReturns one product template whole as Yoplanning sends it: duration, prices and price variations, taxes, participant settings, online selling and voucher settings, translated texts.
list_productsList productsGETLists the team's product templates (the activities sessions are created from), returned whole as Yoplanning sends them. Resold products of other teams are not listed: use list_online_products.

Provider, 2 operations

get_providerGet providerGETReturns one provider team: name, address, phone number, currency, country, language, terms URL and external id.
list_providersList providersGETLists the provider teams whose products this team may resell: name, address, phone, currency, country, language and terms URL. Paginated.

Session, 2 operations

get_sessionGet sessionGETReturns one session: start and end date, place, capacity, staff ids, product, time zone, note and participants (client and quantity).
update_sessionUpdate sessionPUTUpdates a session (dates, capacity, staff, participants). Read it with get_session without expand, change it and send it whole: Yoplanning warns that a partial update may lose data.

Staff fee, 2 operations

get_staff_feeGet staff feeGETReturns one staff fee: its items (session and price), global price, currency, reference, period start and end dates, and the biller.
list_staff_feesList staff feesGETLists the team's staff fees (what staff bill for the sessions they ran): items per session, global price, currency, reference, period and biller. Paginated.

Team, 2 operations

get_teamGet teamGETReturns one team: name, address, phone, currency, country, language, terms URL, email, vendor_id, whether prices include tax, and legal identifiers (SIREN, SIRET, NAF_APE, VAT_NUMBER).
list_teamsList teamsGETLists the teams (schools, structures) the API token has permissions on: name, address, phone, currency, country, language, email and vendor_id. The team id is needed by almost every other tool.

Availability, 1 operation

list_product_availabilitiesList product availabilitiesGETLists the bookable session groups of one online product: dates, tickets left, capacity, standard and other prices (such as child). Send start_date__gt and start_date__lt to bound the dates.

Availability detail, 1 operation

get_availability_optionsGet availability optionsGETReturns the options (such as helmet type) that can be sold with one session group, each listing the resources still in stock with their price and taxes. Use the resource id and session group id in create_order.

Cancel, 1 operation

cancel_orderCancel orderPOSTCancels an order. On hold: the order is deleted and gives back places, stock and vouchers. Confirmed: it becomes CANCELLED and keeps its payments (nothing is refunded). Refused for a locked order.

Confirm, 1 operation

confirm_orderConfirm orderPOSTConfirms an order on hold: it becomes CONFIRMED and keeps its places. Yoplanning emails the booking to the client unless send_email is 0. Record the payment afterwards with create_order_payment.

Extend, 1 operation

extend_orderExtend orderPOSTAdds expiration_minutes to the expiry of an order on hold, so its places stay held longer while the client pays. Refused when the order is not on hold.

Order validation, 1 operation

validate_orderValidate orderPOSTChecks, before the client pays, that an order can still be placed: send the same items as create_order. Answers success, or lists the session groups, resources and vouchers no longer available. Creates nothing.

Reseller, 1 operation

list_resellersList resellersGETLists the reseller teams authorized to sell this team's products: name, address, phone, currency, country, language and terms URL. Paginated.

Use discount, 1 operation

apply_discount_codeApply discount codePOSTApplies a promo code to an existing order. Answers success, the errors (code and description, such as a promo code that does not exist) and the order.

Use Yoplanning from Claude Code, Cursor or Codex

Connect Yoplanning in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Yoplanning operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Yoplanning

Create your workspace
Sign up free. Nothing to install.
Connect Yoplanning once
Add your Yoplanning connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.