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
Chef

Chef Nodes API

The Nodes API from Chef — 3 operation(s) for nodes.

Documentation Provider Profile APIs.io OpenAPI GitHub

Chef Nodes API is one of 14 APIs that Chef publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 6 operations across 3 paths. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://{automate}/api/v0, https://{server}/organizations/{org}.

6 operations 3 paths 0 schemas 1 DELETE3 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://chef.example.com/organizations/example
Authentication
API Key, API Key
Contact
Chef Software
Resource Areas
1

Authentication & Security 2

Chef Nodes API declares 2 security schemes for authenticating requests. An API key is passed in the header as api-token (apiToken). An API key is passed in the header as X-Ops-Authorization (chefSignedAuth).

  • apiToken — API token issued through the Chef Automate UI or admin API.
  • chefSignedAuth — Chef signed-header authentication using an RSA key associated with a client.

Paths & Operations 6

Across 3 paths, the API surfaces 6 operations — 1 DELETE, 3 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Nodes 6
GET
/cfgmgmt/nodes
List configuration management nodes
listManagedNodes → 200
GET
/nodes
List nodes
listNodes → 200
POST
/nodes
Create a node
createNode body → 201
GET
/nodes/{nodeName}
Get a node
getNode 1 param → 200
PUT
/nodes/{nodeName}
Update a node
updateNode 1 param body → 200
DELETE
/nodes/{nodeName}
Delete a node
deleteNode 1 param → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

chef-nodes-api-openapi.yml Raw ↑

Other APIs Chef publishes across the network.

Chef InSpec
AE Profile APIs.io
Chef Channels API
AE Profile APIs.io
Chef Clients API
AE Profile APIs.io
Chef Cookbooks API
AE Profile APIs.io
Chef Data Bags API
AE Profile APIs.io
Chef Environments API
AE Profile APIs.io
Chef IAM API
AE Profile APIs.io
Chef Packages API
AE Profile APIs.io
Chef Profiles API
AE Profile APIs.io
Chef Reports API
AE Profile APIs.io
Chef Roles API
AE Profile APIs.io
Chef Scans API
AE Profile APIs.io
#Nodes
← Back to C APIs
API Details
ID
chef:chef-nodes-api
Base URL
https://chef.example.com/organizations/example
Docs
https://docs.chef.io/server/api_chef_server/
Provider
Chef
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=chef-nodes-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/chef-nodes-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 Chef Nodes 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.