RegFox API Documentation

This is the complete API documentation for connecting to the RegFox API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.

MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.

Meet RegFox: RegFox is an event registration and ticketing platform for forms, orders, registrants, tickets, subscriptions, customers, memberships, coupons, inventory, and webhooks. Keep reading to get started.

Quickstart

Before you run your first RegFox request, you need three things:

1. A MindCloud account — sign in or create an account at MindCloud.
2. A MindCloud API Key — create one in API Keys. Keep it on your server.
3. At least one RegFox connection — create or choose one in Connections. Note its connectionId.

Every RegFox action uses the same URL pattern:

https://connect.mindcloud.co/v1/universal/regFox/latest/actions/{actionSlug}

You need a MindCloud API Key and a RegFox connection. Then call an action such as Get Coupon:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/regFox/latest/actions/get-coupon" \
  --header "Authorization: Bearer $MINDCLOUD_API_KEY" \
  --get \
  --data-urlencode "connectionId=$CONNECTION_ID"

Every response comes back in the same envelope, with your rows in a data array:

{
  "success": true,
  "data": [
    { "id": "1042", "name": "Ava" }
  ],
  "meta": {}
}

After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.

Authentication

Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected RegFox account that should run the action. MindCloud stores and refreshes the RegFox credentials behind that connection, so you never send provider tokens with your requests.

Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.

RegFox actions

All 30 published actions for this RegFox version. Each page documents the endpoint, arguments, and response controls.

• PUTCheck In Registrant
• POSTCreate Coupon
• POSTCreate Webhook
• DELETEDelete Coupon
• DELETEDelete Webhook
• GETGet Coupon
• GETGet Customer
• GETGet Form
• GETGet Membership
• GETGet Order
• GETGet Registrant
• GETGet Subscription
• GETGet Ticket
• GETGet Transaction
• GETGet Webhook
• GETList Form Coupons
• GETList Form Inventory
• GETList Forms
• GETList Global Coupons
• GETList Webhooks
• GETPing
• GETSearch Customers
• GETSearch Memberships
• GETSearch Orders
• GETSearch Registrants
• GETSearch Subscriptions
• GETSearch Tickets
• GETSearch Transactions
• PUTUpdate Coupon
• PUTUpdate Webhook

Related apps

More Marketing apps on the Universal API, behind the same REST shape. Or browse all apps.

Google FormsMailchimpCalendlyWebflowGoogle AdsActiveCampaignBrevoMailerLite