Notepm Jp NotePM API
★ Only Publicly Available OpenAPI DocumentProductivityNote Takingbearer17 EndpointsREST
For Agents
Create, read, update, and search notes, folders, and tags in a NotePM team workspace, plus access comments, attachments, users, and groups.
Use for: I want to create a new meeting note in the Engineering folder, List all notes tagged with 'incident-postmortem', Update the body of an existing onboarding document, Find all folders under the Sales workspace
Not supported: Does not handle real-time collaborative editing, video calls, or task management — use for note creation, folder organisation, and team knowledge retrieval only.
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.
Install Jentic One Beta
Connect the NotePM API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NotePM API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with NotePM API.
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
Patterns agents use NotePM API for, with concrete tasks.
★ 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.
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.
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.
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.
Look up notes tagged 'expense-policy' in NotePM, fetch the most recent one's content, and summarise the answer for the employee
Key Endpoints
17 endpoints — jentic publishes the only available openapi specification for notepm api, keeping it validated and agent-ready.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
NotePM bearer access tokens are stored encrypted in the Jentic vault. Agents receive scoped execution access — the raw token never enters the agent's prompt or context.
Intent-based discovery
Agents search Jentic by intent (e.g. 'create a meeting note') and Jentic returns the matching NotePM operation with its input schema, so the agent calls /notes or /folders correctly without browsing docs.
Time to first call
Direct NotePM integration: half a day for auth and folder hierarchy handling. Through Jentic: minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using NotePM API through Jentic.
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 at https://app.jentic.com/sign-up.
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.
GET STARTED