Neon CRM API Reference

Name: Neon CRM API Reference API
Brand: Neon CRM API Reference
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMContact ManagementapiKey, oauth2276 EndpointsREST

For Agents

Manage nonprofit constituents, donations, memberships, events, and recurring giving in Neon CRM through 276 v2 endpoints.

Use for: Record a $250 donation against a constituent account, Search for a Neon CRM account by email address, Set up a monthly recurring donation for a donor, Register a constituent for an upcoming event

Not supported: Does not handle payment card processing, accounting reconciliation, or grant management workflows - use for nonprofit constituent, donation, and event records in Neon CRM only.

Jentic publishes the only available OpenAPI specification for Neon CRM API Reference, keeping it validated and agent-ready. Neon CRM is a constituent relationship management platform built for nonprofits, with donations, memberships, events, volunteers, and grants in a single record. The 276 v2 endpoints cover account search, donations, payments, recurring giving, event registration, household management, and custom field configuration so a nonprofit can wire fundraising forms, payment processors, and reporting dashboards directly into the constituent record.

Jentic One on Github View OpenAPI Document

Install Jentic One Beta

Connect the Neon CRM API Reference to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Neon CRM API Reference, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fneoncrm.com%2Fneoncrm" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fneoncrm.com%2Fneoncrm" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Neon CRM API Reference API.

Search and link nonprofit constituent accounts using /accounts/search and /accounts/link

Record one-time and recurring donations against a constituent account

Manage household and company relationships between accounts so giving rolls up correctly

GET STARTED

Start building with Neon CRM API Reference API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Neon CRM API Reference API for, with concrete tasks.

★ Online Donation Form Backend

Nonprofits wire donation forms on their own website to /accounts/search and the donations endpoints under /accounts. The form looks up an existing account by email, creates a new account if missing, and records the gift with payment details - so a one-time donation lands in the constituent record without a manual export.

Look up the Neon CRM account for donor@example.com, then record a one-time $100 donation tied to that account.

Recurring Giving Programs

Development teams use Neon CRM v2 endpoints to enroll donors in monthly giving, retry failed charges, and report on recurring revenue. The recurring donation resources under /accounts and the dedicated payment endpoints model the schedule, payment method, and lifecycle, so a sustainer programme runs without ad-hoc spreadsheet tracking.

Enroll the account for donor@example.com in a $25 monthly recurring donation tied to a saved payment method.

Event Registration Backend

Nonprofits run galas, walks, and webinars through the Neon CRM events module. The events endpoints expose sessions, ticket types, and registrations, so an external registration page can take payment and create the registration in Neon CRM in one flow rather than a nightly batch reconciliation.

Major Gift Prospecting

Major-gift teams pull the /accounts/windfall endpoint for capacity signals and combine it with /accounts/search to surface candidates inside their existing constituent base. This replaces standalone wealth-screening exports with a programmatic flow tied to the same account record fundraisers already work in.

Run the windfall lookup for an account and return the capacity rating and the donor identifier.

AI Agent Integration via Jentic

An AI agent uses Jentic to create accounts, record donations, and register attendees in Neon CRM. Jentic exposes the most-used Neon CRM operations by intent, so an agent given a donor email and an amount can find the account, create a new one if missing, and record the gift without hand-coded HTTP calls.

Use Jentic to search for record a donation in neon crm, load the schema, and record a $50 gift for donor@example.com.

Key Endpoints

276 endpoints — jentic publishes the only available openapi specification for neon crm api reference, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/accounts

List constituent accounts

POST

/accounts/search

Search constituent accounts

POST

/accounts/link

Link two accounts as a household

POST

/accounts/unlink

Unlink two accounts

GET

/accounts/search/searchFields

List supported search fields

GET

/accounts/search/outputFields

List supported output fields

GET

/accounts/{id}

Get an account by id

GET

/accounts/windfall

Get windfall capacity signal

GET

/accounts

List constituent accounts

POST

/accounts/search

Search constituent accounts

POST

/accounts/link

Link two accounts as a household

POST

/accounts/unlink

Unlink two accounts

GET

/accounts/search/searchFields

List supported search fields

GET

/accounts/search/outputFields

List supported output fields

GET

/accounts/{id}

Get an account by id

GET

/accounts/windfall

Get windfall capacity signal

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Neon CRM API by hand means choosing between the X-API-KEY and OAuth client secret, building the constituent, donation, and event search payloads, and paging through the large reference yourself. Through Jentic you install once, import Neon CRM from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Neon CRM puts the account id in the URL path (/accounts/{id}), so a rule can pin your agent to one constituent account: it can read that account and nothing else. You choose the operations it may call, so account linking or unlinking is not included unless you add it.

Credential isolation

Your Neon CRM X-API-KEY or OAuth client secret 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.

Intent-based discovery

Agents search Jentic by intent such as 'record a donation' or 'search constituent accounts', and Jentic returns the matching Neon CRM operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Neon CRM API Reference API through Jentic.

Why is there no official OpenAPI spec for Neon CRM API Reference?

Neon One does not publish a standards-validated OpenAPI specification - its developer portal hosts the v2.11 schema in YAML form. Jentic maintains a validated spec so AI agents and developers can call Neon CRM via structured tooling kept up to date with the live API. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Neon CRM API use?

Neon CRM v2 supports two schemes: an API key passed in the X-API-KEY header and OAuth 2.0 for delegated access. Jentic stores either credential encrypted in your Jentic One instance and injects it at execution time, so the raw secret never reaches the agent context.

Can I record a recurring donation through the Neon CRM API?

Yes. The v2 spec covers recurring donation resources tied to a constituent account, including schedule, payment method, and lifecycle status. An external donation form can enroll a sustainer in a monthly programme and Neon CRM tracks subsequent charges in the constituent record.

How do I search for a constituent in Neon CRM through Jentic?

Search Jentic for search neon crm accounts, load the schema for POST /accounts/search, then execute with the search field (for example, email) and the desired output fields. The full flow is pip install jentic, search, load, execute.

What are the rate limits for the Neon CRM API?

Neon CRM does not document explicit per-second rate limits in the spec. Treat the API as a write-moderate, read-heavy service: page through /accounts results rather than dumping the full set, and back off when 429 responses appear.

Can I read custom field configuration through the API?

Yes. /accounts/search/searchFields and /accounts/search/outputFields list the standard and custom fields available to filter and project. Use them when building dynamic search forms or reports against Neon CRM.

Can I limit what my agent is allowed to do with the Neon CRM API?

Yes. Jentic One runs self-hosted, so your own rules decide which Neon CRM operations and credentials the agent may use. Because the account id sits in the URL path at /accounts/{id}, you can pin the agent to a single constituent account so it reads that record and nothing else. You also choose the exact operations it may call, so account linking through /accounts/link and unlinking through /accounts/unlink stay off unless you add them.

Neon CRM API Reference

Connect the Neon CRM API Reference to your agent

Capabilities

Start building with Neon CRM API Reference API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs