How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Neon One

Neon One Custom Fields API

Standard custom fields and the Custom Objects framework.

Documentation Provider Profile APIs.io OpenAPI GitHub

Neon One Custom Fields API is one of 12 APIs that Neon One publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Custom Fields. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 18 operations across 9 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 2.11.

Requests are made against 2 base URLs: https://api.neoncrm.com/v2, https://trial.z2systems.com/v2.

18 operations 9 paths 3 schemas 2 DELETE9 GET1 PATCH4 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.11
Base URL
https://api.neoncrm.com/v2
Authentication
HTTP Basic
Contact
Neon One Developer Center
License
Proprietary
Resource Areas
1

Authentication & Security 1

Neon One Custom Fields API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • basicAuth — HTTP Basic Authentication. Username is the Neon CRM organization's Org ID; password is an API key generated for a system user under Settings User Management.

Paths & Operations 18

Across 9 paths, the API surfaces 18 operations — 2 DELETE, 9 GET, 1 PATCH, 4 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Custom Fields 18

Standard custom fields and the Custom Objects framework.

GET
/customFields
List standard custom fields
listCustomFields 2 params → 200401
POST
/customFields
Create a standard custom field
createCustomField body → 200401
GET
/customFields/{id}
Retrieve a standard custom field
getCustomField 1 param → 200404
PUT
/customFields/{id}
Update a standard custom field
updateCustomField 1 param body → 200404
GET
/customObjects
List custom objects
listCustomObjects → 200401
POST
/customObjects
Create a custom object
createCustomObject body → 200401
GET
/customObjects/{idOrApiAlias}
Retrieve a custom object
getCustomObject 1 param → 200404
PUT
/customObjects/{idOrApiAlias}
Update a custom object
updateCustomObject 1 param body → 200404
PATCH
/customObjects/{idOrApiAlias}
Partially update a custom object
patchCustomObject 1 param body → 200404
DELETE
/customObjects/{idOrApiAlias}
Delete a custom object
deleteCustomObject 1 param → 200404
GET
/customObjects/{idOrApiAlias}/fields
List fields on a custom object
listCustomObjectFields 1 param → 200401
POST
/customObjects/{idOrApiAlias}/fields
Create a field on a custom object
createCustomObjectField 1 param body → 200401
GET
/customObjects/{idOrApiAlias}/records
List records of a custom object
listCustomObjectRecords 1 param → 200401
POST
/customObjects/{idOrApiAlias}/records
Create a record of a custom object
createCustomObjectRecord 1 param body → 200401
GET
/customObjects/{idOrApiAlias}/records/{id}
Retrieve a record of a custom object
getCustomObjectRecord 2 params → 200404
DELETE
/customObjects/{idOrApiAlias}/records/{id}
Delete a record of a custom object
deleteCustomObjectRecord 2 params → 200404
GET
/customObjects/masterDetailObjects
List master/detail custom objects
listMasterDetailObjects → 200
GET
/customObjects/lookUpObjects
List lookup custom objects
listLookUpObjects → 200

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are CustomField (6 properties), CustomObject (4 properties), Error (1 property). Each schema is shown below with its type and property counts.

CustomObject
object
4 properties
CustomField
object
6 properties
Error
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

neonone-custom-fields-api-openapi.yml Raw ↑

Other APIs Neon One publishes across the network.

Neon One Accounts API
AE Profile APIs.io
Neon One Campaigns API
AE Profile APIs.io
Neon One Donations API
AE Profile APIs.io
Neon One Events API
AE Profile APIs.io
Neon One Households API
AE Profile APIs.io
Neon One Memberships API
AE Profile APIs.io
Neon One Orders API
AE Profile APIs.io
Neon One Properties API
AE Profile APIs.io
Neon One Store API
AE Profile APIs.io
Neon One Volunteers API
AE Profile APIs.io
Neon One Webhooks API
AE Profile APIs.io
#Custom Fields
← Back to N APIs
API Details
ID
neonone:neonone-custom-fields-api
Base URL
https://api.neoncrm.com/v2
Docs
https://developer.neoncrm.com/accounts/
Provider
Neon One
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=neonone-custom-fields-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/neonone-custom-fields-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Neon One Custom Fields API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.