list_pending_invitations

This is how you find out somebody has asked you to join a workspace or take something on. It always reads the account the token belongs to and needs no workspace.

Each invitation has its Kind (workspace-member, workspace-transfer or project-transfer), the workspace or site it is for in Name, who sent it, when it was sent and when it expires, and for a workspace invitation the Role you are being given. They come newest first, at most 50, and the acceptance token is stripped from the answer.

Accepting is not available over a token. It happens from the emailed link or the pending invitations button in the Modulify sidebar, so the tool tells the client to report what is waiting rather than act on it. See Members and roles.

Request

Call it with a POST to https://api.modulify.ai/v1/list_pending_invitations. It takes no inputs, so send an empty JSON object or no body at all. The token needs the account:read scope.

It only reads and changes nothing, so retrying it is safe.

curl -X POST https://api.modulify.ai/v1/list_pending_invitations \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{}'

Over MCP, the same method is the list_pending_invitations tool.

Inputs

This tool takes no inputs.

Response

Every call answers with the JSON envelope of success, message, data, code and version. data holds the result described above, and on a method that returns a total, count carries it. The response headers carry the call's X-Request-Id and what is left of your per-minute budget in X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. Errors explains every status code a call can answer with.