A studio API key lets an outside tool act on your studio’s data. With it, a Make scenario can add a trainee when someone pays, assign a plan, send a form or open a task. This is different from the Webhook step. The webhook step sends an event out of Perform. An API key lets the tool come in and read or change data. Only studio owners and head coaches can create and revoke keys.

​
Create a key

1

Open Integrations

Go to Business settings, then Integrations. The section is called Perform API keys.
2

Create the key

Click Create key. Under Key name, type a name that tells you which tool uses it, for example “Make.com”. Click Create.
3

Copy the key now

The key is shown once. Click Copy key and paste it into the tool straight away, then click Done.
The key cannot be shown again after you close the window. If you lose it, revoke it and create a new one. Treat the key like a password. Anyone holding it can act for your studio.
The key list shows each key’s name, the first characters of the key, when it was created and when it was last used. A key that has never been used says Never used.

​
Connect the tool

In Make, add the Perform connection and paste the key when asked. Make checks the key and shows your studio’s name when the connection works. Any other tool that can send web requests with a key in the header works the same way. Developers can find the technical reference in the API overview. Each key belongs to one studio. Everything the tool reads or changes is limited to that studio.

​
What a connected tool can do

​
Things to know before you build a scenario

  • Avoid duplicate trainees. Give each new trainee a stable ID from the source system, such as the spreadsheet row or the payment ID. If the scenario runs again with the same ID, Perform returns the existing trainee and does not create a second one.
  • Duplicate phone numbers. Without that ID, you choose what happens when the phone already exists: stop with an error, return the existing trainee, or update them. The default is to stop with an error.
  • Invites are off by default. Creating a trainee does not send a WhatsApp invite unless the scenario asks for it.
  • Notifications. Assigning a plan or a subscription sends the usual push to the trainee. For bulk imports, switch the notification off in the scenario so trainees are not flooded.
  • Plans with no fixed length. When a plan does not set a duration, the scenario must send one, or the assignment is refused with a message that names the plan.
  • Deleting a trainee needs an explicit confirmation in the scenario. It erases the trainee’s history and cannot be undone.
  • Phone numbers can be sent in any common format. Perform stores them in one standard form.

​
Events a tool can receive

A connected tool can ask Perform to notify it the moment a form is filled. In Make this is the instant “form filled” trigger. The tool registers and removes the subscription by itself when you switch the scenario on and off, so there is nothing to set up in Perform. You can limit the trigger to one form, or leave it open for every form. When a trainee submits a form, the tool receives:
  • The form’s name and type.
  • The trainee’s name, phone, email and the ID your tool gave them, if any.
  • Every answer, with the field label next to the value, in the order the trainee saw them.
  • The submission number, meaning whether this is the trainee’s first, second or later form.
  • A link to the signed document, when the form was a document to sign.
“Form filled” is the only event a tool can subscribe to today. For other events, add a Webhook step to the matching automation. If the tool is down, Perform retries the delivery up to 5 times with growing gaps. Each message is signed so the tool can verify it came from Perform.

​
Revoke a key

  1. Go to Business settings, then Integrations.
  2. Click Revoke key on the key.
  3. Confirm.
The key stops working immediately and any tool using it disconnects. Revoked keys stay in the list with a Revoked badge. Revoke a key when a team member who had it leaves, when you stop using a tool, or when you think the key was exposed.

​
Audit trail

Every change a tool makes with a key is recorded by Perform with that key as the actor. If trainees or subscriptions change unexpectedly, ask Perform support to check which key made the change.

​
Limits

  • Lists come back 50 at a time by default and up to 200 at a time.
  • Requests are rate limited. A scenario that sends too many requests in a short time is asked to slow down.

Webhooks

Send automation events out of Perform.

Limits

All automation limits in one place.