canonical: https://jentic.com/apis/addmembers.com/addmembers

# Addmembers Zivvy RainMaker Web Forms API

Jentic publishes the only available OpenAPI specification for Zivvy RainMaker Web Forms API, keeping it validated and agent-ready. Zivvy RainMaker is a member-management platform used primarily by martial arts schools and similar membership businesses to capture new prospects from their websites. The web forms API has a narrow surface area - one POST that accepts a web lead and one GET that returns the available age groups so the calling form can render a matching dropdown. Authentication is an API key passed as the apikey query parameter.

## For AI agents

Submit web leads and retrieve age-group options for Zivvy RainMaker, the membership platform used by martial arts schools and similar businesses. Used to wire custom signup forms into RainMaker without iframes.

## Scope

Does not list, update, or delete existing leads, manage memberships, or process payments - use for new web-lead intake and age-group lookup only.

## Capabilities

- Submit a prospective member as a web lead with name, contact details, and selected age group
- Retrieve the list of available age groups configured for the RainMaker account
- Capture leads from a custom-built signup form rather than RainMaker's hosted iframe
- Pass the lead through to the RainMaker dashboard so staff can follow up via the standard CRM flow

## Use cases

### Custom website signup form to RainMaker

Martial arts and membership schools that want their signup form to match the rest of their site build it in their own framework instead of embedding the RainMaker iframe. They GET /  to fetch the age groups and render the correct dropdown, then POST /  with the prospect's details when the form is submitted. The lead lands in the RainMaker dashboard exactly as if it had come through the hosted form.

Example prompt: On page load, GET /  to fetch age groups and populate a dropdown; on form submit, POST /  with the prospect's name, email, phone, and selected age_group.

### Lead intake from third-party landing pages

Schools running paid ads to a separate landing page (e.g., Unbounce, ClickFunnels) need that page to drop leads into RainMaker. A serverless function in front of the form calls POST /  with the prospect data, completing the intake without manual export-import. Conversion data therefore reflects in the RainMaker dashboard within seconds.

Example prompt: Receive the form submission webhook from the landing-page tool and POST /  to RainMaker with the contact's name, email, phone, and chosen age_group.

### Age group sync for multi-form deployment

Schools running multiple promotions (kids camp, adult kickboxing, family bundle) keep one source of truth for age categories - the RainMaker account configuration. Pulling the age groups via GET /  at build time guarantees every form's dropdown matches what RainMaker will accept on submission, avoiding rejected leads from typos or stale options.

Example prompt: Run GET /  in a build step and write the returned age groups to the form's config so each landing page renders the same options as the live RainMaker account.

### AI agent for lead capture via Jentic

A lead-capture agent on a school's chat widget asks visitors for their name, contact info, and child's age, then submits the lead to RainMaker through Jentic. The agent searches 'submit a rainmaker web lead', loads the POST schema, fills the fields, and confirms submission to the visitor - all without ever seeing the apikey, which Jentic stores in your Jentic One instance.

Example prompt: Use Jentic to search 'submit zivvy rainmaker web lead', load the POST /  schema, and execute with the visitor's contact details and selected age group.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/` | Add a web lead |
| GET | `/` | Get age groups |

## Key resources

- **WebLead** — A prospective member submission containing name, contact info, and the selected age group.
- **AgeGroup** — A configured class or program category exposed by the RainMaker account, returned for use in form dropdowns.

## Why Jentic

- **Setup:** Wiring the Zivvy RainMaker Web Forms API by hand means appending the apikey to the request URL on every call and mapping web-lead intake onto its two endpoints without a published spec. Through Jentic you install once, import the RainMaker Web Forms API from the API Directory, store the apikey once, and your agent calls it.
- **Permission scoping:** Both endpoints route through the same base path with no resource id in the URL, so limit the agent to the operations it needs, such as submitting a new web lead. You choose the operations it may call, so the age-group lookup is not included unless you add it.
- **Credential handling:** Your Zivvy RainMaker apikey is stored once, encrypted, by your own Jentic One instance and appended to the request URL at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'submit a martial arts school web lead', and Jentic returns the matching RainMaker operation with its input schema so the agent calls the right endpoint without browsing the reference docs, which matters because Zivvy does not publish a public OpenAPI spec.

## Related APIs

- **HubSpot API** — General-purpose CRM that competes with RainMaker for membership-style businesses with broader CRM needs.
- **Insightly CRM API** — SMB CRM with contact and pipeline endpoints suited to small membership businesses.
- **MailerLite API** — Email marketing tool used to follow up with captured leads after RainMaker intake.

## FAQ

### Why is there no official OpenAPI spec for Zivvy RainMaker Web Forms API?

Zivvy does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Zivvy RainMaker Web Forms API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Zivvy RainMaker Web Forms API use?

The API uses an API key passed as the apikey query parameter on every request. In Jentic the key is stored encrypted in your Jentic One instance and appended at execute time so it never appears in agent context, even though it travels on the URL.

### Can I list the configured age groups before submitting a lead?

Yes. GET / on the RainMaker/api base returns the age-group options for the account. Calling it before rendering a form lets the dropdown match the live RainMaker configuration so submissions are not rejected for unknown values.

### How do I submit a lead to RainMaker through Jentic?

Search Jentic for 'submit zivvy rainmaker web lead', load the POST / schema, and execute with the prospect's name, email, phone, and the chosen age_group value. Jentic appends the apikey from the vault and returns the submission result.

### Are there rate limits on the Zivvy RainMaker Web Forms API?

Zivvy does not document explicit rate limits in this spec; in practice the surface is sized for human form-submission traffic. Treat any 429 surfaced through Jentic as a back-off signal and avoid bulk-submitting hundreds of leads in one burst.

### Does this API let me list or update existing leads?

No. The Web Forms API only handles new lead intake and age-group lookup. Listing or updating existing prospects requires the main RainMaker dashboard or a separate Zivvy admin API outside this spec.

### Can I limit what my agent is allowed to do with the Zivvy RainMaker Web Forms API?

Yes. Because you run Jentic One yourself, your own rules decide which of this API's operations the agent may call, and both endpoints share the same base path with no resource id in the URL. You can allow the agent only to submit a new web lead (POST /) while excluding the age-group lookup (GET /) unless you choose to add it. The apikey stays under your control, stored encrypted by your own instance and appended at execution time so the agent never handles it directly.