domain: ERPNext REST API · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Generate an API key and API secret for the integration user in ERPNext (User Settings > API Access); all requests are authenticated with the header 'Authorization: token YOUR_KEY:YOUR_SECRET'.
To read a list of documents GET /api/resource/DOCTYPE, using query parameters filters (URL-encoded JSON array of filter triples), fields, limit_start, and limit_page_length.
To read a single document GET /api/resource/DOCTYPE/DOCNAME; the response 'data' object contains all fields.
To create, POST to /api/resource/DOCTYPE with a JSON body of field values; the response returns the new document name (string ID).
To update, PUT to /api/resource/DOCTYPE/DOCNAME with only the changed fields; to delete, DELETE to /api/resource/DOCTYPE/DOCNAME (only permitted on draft or cancelled documents).
Known gotchas
ERPNext document names are string identifiers (e.g., 'SINV-00001'), not integer IDs; treat them as opaque strings rather than assuming an incrementing pattern.
Submitted documents (docstatus=1) cannot be directly edited via PUT; they must be cancelled (POST to /api/resource/DOCTYPE/DOCNAME/cancel) and then amended, which creates a new document.
Child table rows in a document (e.g., items in a Sales Invoice) must be included as a complete array on every PUT; a partial array will replace the existing rows, not merge them.
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?