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

# Wild Apricot Admin API

This is Wild Apricot's API for administrators. You can use it if you already have a Wild Apricot account (typically with a website on *.wildapricot.org). Otherwise, please use https://register.wildapricot.com to create a new account. If you have any questions about this API, please contact our support team at support@wildapricot.com. The API exposes 107 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically base url for specific API version., list of available accounts. Covers 107 operations with oauth2 authentication.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- Base URL for specific API version.
- List of available accounts
- Details for specific account
- Create a new contact or member record
- Contacts list
- Retrieve information about current contact

## Use cases

### CRM Operations

Use the Wild Apricot Admin API to perform crm operations programmatically. The API provides 107 endpoints covering core functionality including base url for specific API version., list of available accounts, details for specific account.

Example prompt: Call GET / to base url for specific API version.

### Automated Accounts Management

Automate accounts operations by combining multiple Wild Apricot Admin API endpoints. Agents can list of available accounts and then details for specific account in a single workflow.

Example prompt: Call GET /accounts to list of available accounts, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Wild Apricot Admin API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle oauth2 tokens manually.

Example prompt: Search Jentic for 'base url for specific API version.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/` | Base URL for specific API version. |
| GET | `/accounts` | List of available accounts |
| GET | `/accounts/{accountId}` | Details for specific account |
| POST | `/accounts/{accountId}/contacts` | Create a new contact or member record |
| GET | `/accounts/{accountId}/contacts` | Contacts list |
| GET | `/accounts/{accountId}/contacts/me` | Retrieve information about current contact |
| GET | `/accounts/{accountId}/contacts/{contactId}` | Retrieve information about specific member or contact |
| PUT | `/accounts/{accountId}/contacts/{contactId}` | Update information about existing member or contact |

## Key resources

- **Accounts** — Operations related to Accounts
- **Attachments** — Operations related to Attachments
- **Contacts** — Operations related to Contacts
- **Contacts.CustomFields** — Operations related to Contacts.CustomFields
- **Contacts.SavedSearch** — Operations related to Contacts.SavedSearch

## Why Jentic

- **Setup:** Wiring the Wild Apricot Admin API by hand means running its OAuth flow against oauth.wildapricot.org, targeting the separate api.wildapricot.org host, and threading the account id through every call yourself. Through Jentic you install once, import the Wild Apricot Admin API from the API Directory, store the OAuth client once, and your agent calls it.
- **Permission scoping:** Wild Apricot puts the account and contact ids in the URL path (`/accounts/{accountId}/contacts/{contactId}`), so a rule can pin your agent to one account and the contacts within it. You choose the operations it may call, so writes like updating a contact are not included unless you add them.
- **Credential handling:** Your Wild Apricot OAuth client is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list contacts for an account' or 'create a contact', and Jentic returns the matching Wild Apricot operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Wild Apricot Admin API use?

The Wild Apricot Admin API uses OAuth 2.0 for authorization. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I base url for specific API version. with the Wild Apricot Admin API?

Yes. Use the GET / endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Wild Apricot Admin API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I base url for specific API version. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'base url for specific API version.'. Jentic returns the matching Wild Apricot Admin API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Wild Apricot Admin API have?

The Wild Apricot Admin API exposes 107 endpoints covering accounts, attachments, contacts operations.

### Can I limit what my agent is allowed to do with the Wild Apricot Admin API?

Yes. Because you self-host Jentic One, your own rules decide which Wild Apricot operations and credentials the agent may use. Since the account and contact ids sit in the URL path, such as `/accounts/{accountId}/contacts/{contactId}`, you can pin the agent to a single account and the contacts within it. You also choose the exact operations it may call, so read-only calls like listing contacts can be permitted while writes such as updating a contact stay off unless you add them.