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

# Novi AMS API

Novi AMS is an association management system that runs trade and professional associations end-to-end - membership, events, content, ecommerce, committees, and credentials. The API exposes 78 endpoints covering members, activities, events, blogs, committees, ecommerce, custom fields, groups, and credits, each scoped to the association's own Novi AMS domain. It supports the operational tasks of integrating an association website with downstream systems for member data, event registrations, and dues processing. Novi AMS publishes its own API reference as a Postman collection, and this page describes a curated, agent-optimized Jentic OpenAPI specification converted from that source.

## For AI agents

Read and update association members, events, activities, ecommerce, committees, and credits in a Novi AMS-managed association.

## Scope

Does not handle marketing email campaigns, payroll, or general-purpose CRM pipelines - use for association member, event, and credit management only.

## Capabilities

- List, retrieve, add, and update association member records and member types
- Create activities, retrieve activity details, and assign custom activity types
- Manage events, registrations, and event-related content for the association
- Read and post on association blogs and committee pages
- Process ecommerce purchases tied to membership and event flows
- Apply custom fields to members and activities for association-specific data

## Use cases

### Member Directory Sync

An association's marketing site pulls a public member directory from Novi AMS using the simple member list and member detail endpoints. The integration filters by member type so only currently paid-up members appear, and refreshes nightly so new joiners are visible without manual editing in the association's website CMS.

Example prompt: Pull the simple member list for active member types and publish it as a directory feed for the public website

### Continuing Education Tracking

An association tracks continuing education credits for its members through Novi AMS activities and credits endpoints. When a member completes a course in an external LMS, an integration creates the activity and applies the right credit value, so the member's record stays current without manual data entry by association staff.

Example prompt: Create an activity for a member's completed course with the activity type 'CE Course' and apply 2 credits to the member's record

### Event Registration Pipeline

The association runs a conference registration flow that creates Novi AMS event registrations and ecommerce purchases for ticket fees. The events and ecommerce endpoints together expose the registration record and the payment line item, so finance can reconcile the conference revenue against the member roster.

Example prompt: Register a member for the annual conference, create the matching ecommerce line item, and confirm both records exist on the member

### AI Agent Member Service

An AI assistant in the association's member portal answers questions about credits earned, committee membership, and renewal status. Through Jentic, the agent searches for the right Novi AMS operation, loads the schema, and pulls the supporting data - member detail, activities, credits - without staff intervention.

Example prompt: Look up a member's details, list their activities for the current year, and total their continuing education credits

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/members` | List members |
| POST | `/members` | Add a member |
| GET | `/members/{customerId}` | Get member details |
| PUT | `/members/{customerId}` | Update a member |
| GET | `/members/simple-list` | Get the simple member list |
| POST | `/activities` | Create an activity |
| GET | `/activities` | List activities |

## Key resources

- **Members** — Add, retrieve, update, and list association members and member types
- **Activities** — Create and manage activity records, including custom activity types
- **Events** — Manage events and event registrations
- **Committees** — Read and manage committee structures and membership
- **Ecommerce** — Process ecommerce purchases tied to membership and events
- **Credits** — Track continuing education or earned credits per member
- **Custom Fields** — Define and use association-specific fields on members and activities
- **Groups** — Manage member groups for permissions and segmentation

## Why Jentic

- **Setup:** Wiring Novi AMS by hand means passing your API key as the username in basic auth, resolving your association {domain} host, and threading that through member and activity calls yourself across dozens of endpoints. Through Jentic you install once, import the Novi AMS API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Novi AMS puts the member id in the URL path (`/members/{customerId}`), so a rule can pin your agent to reads and updates on one member. You choose the operations it may call, so creating members or logging activities is not included unless you add it.
- **Credential handling:** Your Novi AMS API key is stored once, encrypted, by your own Jentic One instance and injected at execution time as the basic-auth username. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'add an association member' or 'log a continuing education activity', and Jentic returns the matching Novi AMS operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Wild Apricot API** — Wild Apricot is another association management platform with a similar member, event, and dues model.
- **HubSpot Contacts API** — Sync association members from Novi AMS into HubSpot for marketing automation.
- **Stripe API** — Pair Stripe payments with Novi AMS ecommerce for dues and event fee processing.

## FAQ

### Which OpenAPI specification does this Novi AMS API page describe?

A curated, agent-optimized Jentic OpenAPI specification covering 78 Novi AMS operations. Novi AMS publishes its own API reference as a Postman v2 collection at https://api-docs.noviams.com/api/collections/1247282/S11GQKak?segregateAuth=true&versionTag=latest, which holds 90 requests across 15 top-level folders plus one loose top-level request, and is a Postman collection rather than an OpenAPI document. The Jentic variant converts that source into a validated OpenAPI specification with per-operation input schemas, so agents can discover and call the operations directly. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Novi AMS API use?

Novi AMS uses HTTP basic authentication, with the association's API key passed as the username. Through Jentic, the API key is held in the vault and injected at execution time, so the agent never handles the raw key.

### Can I update member records with the Novi AMS API?

Yes. PUT `/members/{customerId}` updates a member record by id, and POST /members adds a new member. GET `/members/simple-list` is the lightweight directory view, while GET `/members/{customerId}` returns the full record.

### What are the rate limits for the Novi AMS API?

The OpenAPI spec does not declare explicit rate limits. Novi AMS enforces association-level limits in production; consult the Novi AMS docs and back off on 429 responses.

### How do I track continuing education credits through Jentic?

Search Jentic for 'log a continuing education activity'. Jentic returns the POST /activities operation along with the credits-related endpoints, so the agent can create the activity and apply credits in two structured calls.

### Which association domain do I call against?

Each association has its own Novi AMS domain - the base URL template is https://{domain}/api where {domain} is the association's Novi AMS hostname. Set this server variable to your association's domain before calling the API.

### Can I limit what my agent is allowed to do with the Novi AMS API?

Yes. Because you run Jentic One yourself, your own rules decide which Novi AMS operations and credentials the agent may use. Since the member id sits in the URL path (GET and PUT `/members/{customerId}`), you can pin the agent to reading and updating a single member, and grant the simple member list (GET `/members/simple-list`) for directory work. Operations you leave out, such as adding members (POST /members) or logging activities (POST /activities), stay off-limits until you explicitly allow them.