Miro API

What authentication does the Miro API use?

Miro v2 uses HTTP bearer token authentication. Tokens are typically obtained via Miro's OAuth 2.0 install flow and sent in the Authorization header as `Bearer <token>`. Jentic stores the bearer in its vault and injects it per call.

Can I add a sticky note to a Miro board with this API?

Yes. POST /v2/boards/{board_id}/sticky_notes accepts the note text, fill colour, and absolute or frame-relative coordinates. The response includes the new item id, which can be passed to PATCH /v2/boards/{board_id}/items/{item_id} to move or restyle it later.

How do I draw a connector between two items?

First create the source and target items (shape, sticky note, frame, etc.) and capture their item ids. Then POST /v2/boards/{board_id}/connectors with start_item_id and end_item_id; Miro draws the connector between them.

How do I create a Miro board through Jentic?

Run `pip install jentic`, search Jentic for 'create a Miro board', and Jentic returns the POST /v2/boards operation with its input schema. Provide a name and optional description, then execute. The response contains the new board_id.

Can I list members of a Miro organisation?

Yes. GET /v2/orgs/{org_id}/members returns members at the organisation level and GET /v2/orgs/{org_id}/teams returns the teams. Use these endpoints to drive provisioning flows that match Miro access to your directory.

Can I limit what my agent is allowed to do with the Miro API?

Yes. Because you run Jentic One yourself, your own rules decide which Miro operations and which bearer token the agent may use. Since Miro puts the board id and item id in the URL path, such as /v2/boards/{board_id}/items/{item_id}, a rule can pin the agent to a single board so it can add sticky notes and shapes there and nothing else. You pick the operations it may call, so inviting a board member via POST /v2/boards/{board_id}/members stays off limits unless you explicitly allow it.