canonical: https://jentic.com/apis/notepm.jp/notepm # Notepm Jp NotePM API Jentic publishes the only available OpenAPI specification for NotePM API, keeping it validated and agent-ready. NotePM is a Japanese knowledge-sharing and documentation platform used by teams to keep notes, manuals, and meeting records organised in folders with tagging and full-text search. The API exposes 17 endpoints covering notes, folders, tags, comments, attachments, groups, users, and team metadata. It supports the operational tasks of creating documentation, organising it in a folder hierarchy, and exposing team knowledge to other tools. ## For AI agents Create, read, update, and search notes, folders, and tags in a NotePM team workspace, plus access comments, attachments, users, and groups. ## Scope Does not handle real-time collaborative editing, video calls, or task management - use for note creation, folder organisation, and team knowledge retrieval only. ## Capabilities - Create and update notes with body content, tags, and folder placement - Organise content with nested folders, including create, rename, and delete - Tag notes for cross-folder grouping and topical retrieval - Read and post comments on existing notes - Manage attachments tied to a note - List team users and groups for permissions and assignment context ## Use cases ### Automated Meeting Note Capture An automation creates a new NotePM note for each scheduled meeting, populated with the agenda, attendee list, and a link back to the calendar event. After the meeting, the same automation appends a transcript and tags the note for retrieval. The /notes endpoints handle creation and updates; folders organise notes by team or project. Example prompt: Create a new note titled 'Weekly Engineering Sync 2026-06-11' inside the Engineering folder with the agenda content and tag 'weekly' ### Knowledge Base Synchronisation An internal tool mirrors a NotePM folder tree into a search index used by a customer support agent, so support reps can answer product questions grounded in the latest internal documentation. The folders and notes endpoints expose hierarchy and content; tags drive topical filtering on the index side. Example prompt: List all notes inside the Product Documentation folder, fetch each note's content, and push them to the search index with their tags ### Onboarding Documentation Workflow When a new hire joins, an HR automation creates a personalised NotePM folder with copies of standard onboarding notes, then assigns access to the user and their team. The folders, notes, users, and groups endpoints together provide the building blocks for this kind of personalised documentation provisioning. Example prompt: Create a folder 'Onboarding - Aiko Tanaka', copy the three standard onboarding notes into it, and tag each note with 'onboarding-2026' ### AI Agent Documentation Lookup An AI assistant embedded in a chat client answers employee questions about internal processes by retrieving the most relevant NotePM notes. Through Jentic, the agent searches for the right NotePM operation, loads the schema, and pulls note content to ground its answer rather than guessing. Example prompt: Look up notes tagged 'expense-policy' in NotePM, fetch the most recent one's content, and summarise the answer for the employee ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/notes` | List notes | | POST | `/notes` | Create a note | | GET | `/notes/{id}` | Get a note | | PUT | `/notes/{id}` | Update a note | | DELETE | `/notes/{id}` | Delete a note | | GET | `/folders` | List folders | | POST | `/folders` | Create a folder | | GET | `/users` | List users in the team | ## Key resources - **Notes** — Create, read, update, and delete notes with content and tags - **Folders** — Manage folder hierarchy used to organise notes - **Tags** — Apply and list tags for cross-folder grouping - **Comments** — Read and post comments on notes - **Attachments** — Manage files attached to notes - **Users** — List team users for assignment and permissions - **Groups** — List groups used for access control - **Team** — Read team metadata ## Why Jentic - **Setup:** Wiring NotePM by hand means setting up its bearer token, resolving your team subdomain in the {teamDomain}.notepm.jp host, and threading the header through note and folder calls yourself. Through Jentic you install once, import the NotePM API from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** NotePM puts the note id in the URL path (`/notes/{id}`), so a rule can pin your agent to reads and updates on one note. You choose the operations it may call, so a destructive DELETE `/notes/{id}` is not included unless you add it. - **Credential handling:** Your NotePM bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create a meeting note' or 'organise a folder', and Jentic returns the matching NotePM operation with its input schema so the agent calls /notes or /folders without browsing the reference docs. ## Related APIs - **Notion API** — Notion is a richer block-based knowledge platform with database support but a steeper learning curve. - **Atlassian Jira API** — Pair NotePM documentation with Jira issue tracking for engineering teams. - **Coda API** — Coda combines documents and tables in one canvas, while NotePM stays focused on note-and-folder docs. ## FAQ ### Why is there no official OpenAPI spec for NotePM API? NotePM does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call NotePM API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the NotePM API use? NotePM uses HTTP bearer authentication with an access token issued from your NotePM team settings. Through Jentic, the access token is held in the vault and injected at execution time. ### Can I create notes in specific folders with the NotePM API? Yes. POST /notes accepts a folder reference in its body, so you can create notes directly inside a target folder. Use GET /folders to enumerate available folder ids first. ### What are the rate limits for the NotePM API? The OpenAPI spec does not declare explicit rate limits. NotePM applies plan-based limits in production; consult the team domain dashboard and back off on 429 responses. ### How do I list notes by tag through Jentic? Search Jentic for 'list notes by tag in NotePM'. Jentic returns the GET /notes operation with its query parameter schema, including the tag filter, so the agent can call it directly. ### Does the NotePM API support attachments and comments? Yes. The attachments resource exposes files tied to a note, and the comments resource lets you read and post comments. Both work alongside the core /notes endpoints. ### Can I limit what my agent is allowed to do with the NotePM API? Yes. Jentic One is self-hosted, so you run it and your own rules decide which NotePM operations and credentials the agent may use. Because NotePM puts the note id in the URL path (`/notes/{id}`), you can pin the agent to reads and updates on a single note, and grant only the operations you intend, such as GET /notes and POST /notes for creating and retrieving documentation. A destructive call like DELETE `/notes/{id}` is not available to the agent unless you explicitly add it.