canonical: https://jentic.com/apis/peerbie.com/peerbie # Peerbie API Jentic publishes the only available OpenAPI specification for Peerbie API, keeping it validated and agent-ready. Peerbie API provides programmatic access to team collaboration features including posts, issues, todos, and customer management. The API enables teams to create and manage internal communications, track issues and tasks assigned to users, and maintain customer records within network-scoped workspaces. It serves as the backend for team coordination workflows with 8 endpoints across its alpha version. ## For AI agents Manage team posts, issues, todos, and customer records within collaborative workspaces. Programmatic access to Peerbie team coordination features. ## Scope Does not handle video conferencing, file storage, or calendar scheduling - use for team posts, issues, todos, and customer record management only. ## Capabilities - Create and manage team posts for internal communications - Track issues with assignment and status management - Manage user-specific todo lists for task coordination - Maintain customer records scoped to network workspaces - Organize team activities across isolated network contexts ## Use cases ### Team Communication Management Create and retrieve team posts for internal announcements, updates, and discussions. The `/alpha/posts` endpoint handles team communications within the Peerbie workspace, enabling programmatic posting of updates and retrieval of the post feed for integration with other notification systems. Example prompt: POST to `/alpha/posts` with content and metadata to create a team announcement, then GET `/alpha/posts` to verify it appears in the feed ### Issue and Task Tracking Track issues and manage user-scoped todo lists for team coordination. Issues represent work items that need resolution, while todos track individual task assignments. Together they provide a lightweight project tracking system accessible through the API. Example prompt: GET `/alpha/issues` to list all open issues, then GET `/alpha/users/{username}/todos` to check todo items assigned to a specific team member ### Network-Scoped Customer Management Maintain customer records within Peerbie network workspaces. Each network isolates its customer data, enabling multi-team or multi-department customer tracking. The API supports listing customers within a specific network context for CRM-light functionality. Example prompt: GET `/alpha/networks/{network_uid}/customers` to retrieve all customer records for a specific team network ### AI Agent Team Coordination via Jentic AI agents manage team workflows by calling Peerbie through Jentic. The agent searches for team collaboration operations, loads schemas for posts, issues, or todos, and executes without managing CSRF tokens or understanding network scoping directly. Example prompt: Search Jentic for 'create team post', load the `/alpha/posts` operation schema, and execute to post a team update through Peerbie ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/alpha/posts` | List all team posts | | GET | `/alpha/issues` | List all tracked issues | | GET | `/alpha/users/{username}/todos` | Get todos for a specific user | | GET | `/alpha/networks/{network_uid}/customers` | List customers in a network | ## Key resources - **Posts** — Create and manage team communications and announcements - **Issues** — Track work items and bugs for team resolution - **Todos** — Manage user-specific task lists and assignments - **Customers** — Maintain customer records scoped to network workspaces ## Why Jentic - **Setup:** Wiring Peerbie by hand means setting the csrfToken header on every request and threading usernames and network ids through the alpha endpoints yourself. Through Jentic you install once, import the Peerbie API from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Peerbie puts the user and network id in the URL path (`/alpha/users/{username}/todos`, `/alpha/networks/{network_uid}/customers`), so a rule can pin your agent to one user's todos or one network's customers. You choose the operations it may call, so reading posts and issues is included only if you add it. - **Credential handling:** Your Peerbie csrfToken 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 'list a user's todos' or 'read team posts', and Jentic returns the matching Peerbie operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Asana API** — Full-featured project management with tasks, projects, and portfolios - **Slack API** — Real-time team messaging and channel-based communication - **PDF Endpoint API** — Generate PDF reports from HTML for team documentation ## FAQ ### Why is there no official OpenAPI spec for Peerbie API? Peerbie does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Peerbie 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 Peerbie API use? Peerbie API uses a CSRF token passed in the csrfToken header. This token is obtained from your Peerbie session. Through Jentic, token management is handled in the credential vault so agents can make authenticated requests without manual token handling. ### What is the current version status of the Peerbie API? The Peerbie API is in alpha stage, with all endpoints under the /alpha/ path prefix. This means the API interface may change in future versions. The current version provides 8 endpoints covering posts, issues, todos, and customers. ### How are customers scoped in the Peerbie API? Customers are scoped to specific networks identified by a network_uid. Access customer records via GET `/alpha/networks/{network_uid}/customers.` Each network represents an isolated workspace with its own customer data. ### How do I manage team tasks through Jentic with Peerbie? Install with pip install jentic, search for 'list team issues' or 'get user todos'. Jentic returns the `/alpha/issues` or `/alpha/users/{username}/todos` schemas. Execute to retrieve issues or todo items. Jentic handles CSRF token injection automatically. ### Can I get todos for a specific team member? Yes. GET `/alpha/users/{username}/todos` retrieves the todo list for a specific user identified by their username. This returns all task items assigned to or created by that team member. ### Can I limit what my agent is allowed to do with the Peerbie API? Yes. Because you run Jentic One yourself, your own rules decide which Peerbie operations and credentials the agent may use. Since Peerbie puts the user and network id directly in the URL path, you can pin the agent to one user's todos at `/alpha/users/{username}/todos` or one network's customers at `/alpha/networks/{network_uid}/customers.` Read access to team posts and issues is included only if you add those operations, so listing `/alpha/posts` or `/alpha/issues` stays off unless you allow it.