Zapier lets you build automations, called Zaps, that connect your apps. With the Pipeline API, a Zap can create a client in Mindbody when a new lead comes in, create a follow-up task for your team, and more.
This guide shows you how to connect using Zapier's built-in tools for calling an API.
What you need
A Zapier account
Your Pipeline API key
Get your Pipeline API key
To get your Pipeline API key, message us using the chat in Pipeline, or email [email protected], and we'll help.
Pipeline API keys start with ps_key_. Keep your key private: anyone who has it can create clients, sales and tasks for your studio. If you think your key has been shared, contact us and we'll help you replace it.
How authentication works
Send your key in the header Authorization with the value Bearer [your API key] (the word Bearer, a space, then your key).
The header X-API-Key with your key on its own also works.
All requests go to https://api.pipeline-solutions.co/v1. Older integrations that use /api instead of /v1 keep working.
Call the Pipeline API from a Zap
Set up the trigger that starts your Zap, for example a new lead from your form or ads tool.
Add an action step and choose Webhooks by Zapier.
Choose POST to send data (for example to create a client or task) or GET to look something up. Choose Custom Request if you want to type the JSON body exactly.
Enter the URL for the endpoint, for example https://api.pipeline-solutions.co/v1/clients.
Set the payload type to JSON and fill in the fields, mapping values from your trigger.
Under Headers, add Authorization with the value Bearer [your API key].
Test the step with "Test": true in the body, then remove it.
Webhooks by Zapier stores your key in the step, where anyone with access to the Zap can see it. Zapier's API by Zapier app keeps the key in a saved connection instead, so it is the safer choice if others edit your Zaps.
What the Pipeline API can do
These are the actions in our API today:
Check your connection: GET /v1/me returns the organization and studio provider tied to your key.
Find a client by email: GET /v1/clients/search?email=..., optionally narrowed by first_name and last_name. This is a live Mindbody lookup that includes inactive clients.
Create a client: POST /v1/clients. Email is required. If Mindbody already has a client with the same email, first name and last name, we return that client instead of creating a duplicate.
Sell a pricing option: POST /v1/sales sells one Mindbody pricing option to a client.
Create a task: POST /v1/tasks creates a studio task. Only name is required.
Look up studio details: locations, services, client custom fields, referral types, required client fields, and your studio's users.
The client, sale and studio detail endpoints work with Mindbody only. If your studio uses Mariana Tek, message us before you build your Zap and we'll let you know what's available.
If you need more detail on any of these actions, message us and we'll help.
Example requests
Create a client from a new lead
Method POST, URL https://api.pipeline-solutions.co/v1/clients, headers Authorization: Bearer [your API key] and Content-Type: application/json, body:
{"Email": "[lead email]", "FirstName": "[first name]", "LastName": "[last name]", "MobilePhone": "[mobile]", "IsProspect": true, "Test": true}With "Test": true, Mindbody runs in test mode and nothing is saved. Remove it once your test works. Check GET /v1/clients/required-fields first: if your studio requires more fields in Mindbody (for example a birth date or address), include them. Use GET /v1/clients/referral-types to see the allowed values for ReferredBy.
Create a follow-up task
Method POST, URL https://api.pipeline-solutions.co/v1/tasks, same headers, body:
{"name": "Call new lead", "description": "[details]", "client_email": "[lead email]", "assigned_user_email": "[team member email]", "due_date": "YYYY-MM-DD"}Status is optional and defaults to open. Allowed values: open, in progress, blocked, review, completed, archived.
Find a client
Method GET, URL https://api.pipeline-solutions.co/v1/clients/search?email=[email], header Authorization: Bearer [your API key].
If a request fails
A 422 response means a field is missing or in the wrong format. The response lists which field.
A 400 response on client or sale requests can mean the key is not for a Mindbody studio, or Mindbody rejected the request.
A 502 response means Mindbody did not respond or did not confirm the result. If the response says MINDBODY_UNAVAILABLE, nothing was saved and you can try again. If it says MINDBODY_OUTCOME_UNKNOWN, the client or sale may have been created, so check Mindbody before trying again.
A 503 response means your studio's Mindbody connection is not set up or not ready yet. Contact us.
You can check for known issues at status.pipeline-solutions.co.
Still stuck? Send us the request you made (without your API key) and the response at [email protected] or the chat in the portal.
Need help?
Message us using the chat in Pipeline, or email [email protected].
