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.