domain: developer.neoncrm.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Determine your base URL: https://api.neoncrm.com/v2 for production/sandbox instances, or the trial-specific host for trial instances
Authenticate using HTTP Basic Auth with your Neon organization ID as the username and an API key as the password
Ensure the donor's individual or organization account already exists in Neon (create it first via the Accounts endpoints if not) — a donation cannot be created without an existing account
POST to the donations endpoint with the account ID, amount, donation date, and a valid tender/payment type
Optionally associate the donation with a campaign, fund, purpose, or solicitation method by ID (retrievable from their respective list endpoints)
Check the response for the created donation ID and transaction/payment status
Known gotchas
Neon CRM has two distinct API generations — the legacy v1 (SOAP/REST hybrid with dotted parameter names) and the current v2 (OpenAPI/Swagger REST) — do not mix documentation or parameter conventions between them
The account (donor) must exist in Neon before a donation can be attached to it; there is no combined create-account-and-donate call
Campaign/fund/purpose/source values are typically ID references to org-specific picklists, not free text, so they must be fetched from the corresponding list endpoints first
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?