doc/developers-guide/api-reference.md

---
title: API Reference
slug: api-reference
type: link
content:
  excerpt: 'View all API methods, attributes and responses.'
privacy:
  view: public
---
doc: Add guides and GitHub workflow for doc sync This PR: - adds all the guides (in markdown format) that is published at https://docs.corelightning.org/docs - adds a github workflow to sync any future changes made to files inside the guides folder - does not include API reference (json-rpc commands). Those will be handled in a separate PR since they're used as manpages and will require a different github workflow Note that the guides do not exactly map to their related files in doc/, since we reorganized the overall documentation structure on readme for better readability and developer experience. For example, doc/FUZZING.md and doc/HACKING.md#Testing are merged into testing.md in the new docs. As on the creation date of this PR, content from each of the legacy documents has been synced with the new docs. Until this PR gets merged, I will continue to push any updates made to the legacy documents into the new docs. If this looks reasonable, I will add a separate PR to clean up the legacy documents from doc/ (or mark them deprecated) to avoid redundant upkeep and maintenance. Changelog-None 2023-04-22 17:21:44 +04:00			`---`
docs: Updated `developers-guide` docs for v10 2025-11-12 14:32:54 -08:00			`title: API Reference`
			`slug: api-reference`
			`type: link`
			`content:`
			`excerpt: 'View all API methods, attributes and responses.'`
			`privacy:`
			`view: public`
doc: Add guides and GitHub workflow for doc sync This PR: - adds all the guides (in markdown format) that is published at https://docs.corelightning.org/docs - adds a github workflow to sync any future changes made to files inside the guides folder - does not include API reference (json-rpc commands). Those will be handled in a separate PR since they're used as manpages and will require a different github workflow Note that the guides do not exactly map to their related files in doc/, since we reorganized the overall documentation structure on readme for better readability and developer experience. For example, doc/FUZZING.md and doc/HACKING.md#Testing are merged into testing.md in the new docs. As on the creation date of this PR, content from each of the legacy documents has been synced with the new docs. Until this PR gets merged, I will continue to push any updates made to the legacy documents into the new docs. If this looks reasonable, I will add a separate PR to clean up the legacy documents from doc/ (or mark them deprecated) to avoid redundant upkeep and maintenance. Changelog-None 2023-04-22 17:21:44 +04:00			`---`
docs: Updated `developers-guide` docs for v10 2025-11-12 14:32:54 -08:00