Manage the individual pages and folders (entries) that make up your documentation. Using the DocEntry API, you can programmatically create, read, update, organize, and delete content within a specific documentation section.
Because entries belong to a specific section, version, and documentation project, every API request requires a specific set of path parameters to locate the exact content you want to manage.
flowchart LR
Org["Organization"] --> Doc["Documentation"]
Doc --> Ver["Version"]
Ver --> Sec["Section"]
Sec --> Ent["Doc Entry"]
Ent -.-> Sub["Child Entry (Optional)"]All endpoints on this page share the same base path structure:/v1/documentation/{organization_id}/{documentation_id}/version/{version_id}/section/{section_id}/entry
Retrieving Content
You can retrieve entries as a flat list, a hierarchical tree, or fetch a single specific entry by its ID.
| Action | Method | Endpoint | Description |
|---|---|---|---|
| Get all | GET | /.../entry | Returns a flat list of all entries within the specified section. |
| Get tree | GET | /.../entry/tree | Returns entries nested in their parent-child hierarchy. |
| Get single | GET | /.../entry/{entry_id} | Retrieves the content and metadata for a specific entry. |
Creating and Modifying Entries
When adding content, you can create entries one by one or use the batch endpoint to upload multiple pages simultaneously.
| Action | Method | Endpoint |
|---|---|---|
| Create entry | POST | /.../entry |
| Batch create | POST | /.../entry/batch |
| Update entry | PUT | /.../entry/{entry_id} |
| Delete entry | DELETE | /.../entry/{entry_id} |
Deleting a parent entry (like a folder) will permanently delete all of its child entries. This action cannot be undone.
Organizing Your Documentation
As your documentation grows, you may need to restructure your table of contents. The API provides dedicated endpoints for moving and reordering entries without needing to update each entry individually.
| Action | Method | Endpoint | Effect |
|---|---|---|---|
| Move | POST | /.../entry/{entry_id}/move | Moves an entry to a new parent folder or a completely different section. |
| Reorder | POST | /.../entry/reorder | Updates the display order (order property) of multiple entries at once. |
Workflow: Building a section programmatically
If you are migrating content from another system or generating documentation automatically, you can use these endpoints together to build out a complete section.
- 1
Create the parent categories
Use the
POST /.../entryendpoint to create your top-level folders. Save the returnedentry_idfor each folder. - 2
Batch upload the pages
Use the
POST /.../entry/batchendpoint to upload multiple pages at once. Map each page to its respective parent folder using theentry_ids you saved in step 1. - 3
Set the display order
Call
POST /.../entry/reorderwith an array of entry IDs in the exact order you want them to appear in your documentation sidebar.
Can I move an entry to a different version or documentation project?
No. The move endpoint only allows you to move an entry between different sections or parent folders within the same version. To move content across versions or projects, you must recreate the entry in the target location and delete the original.
What is the difference between the flat list and the tree view?
The flat list (GET /.../entry) returns an array of all entries, which is useful for searching or bulk processing. The tree view (GET /.../entry/tree) returns a nested JSON object where child entries are located inside their parent's children array, which is ideal for rendering navigation sidebars.