Yapper API
Api reference
GET
/skills

Returns the MCP server instructions and public prompting-skill catalog used by Yapper's hosted and stdio MCP servers.

Authorization

bearerAuth models:read
AuthorizationBearer <token>

In: header

Scope: models:read

Response Body

application/json

application/json

application/json

application/json

curl -X GET "https://example.com/skills"
{}
{  "error": {    "code": "string",    "message": "string",    "requestId": "string"  }}
{  "error": {    "code": "string",    "message": "string",    "requestId": "string"  }}
{  "error": {    "code": "string",    "message": "string",    "requestId": "string"  }}

List processes GET

Lists team processes visible to the API key. Supports at most one of status, type, or model; sessionId combines with status only. Unsupported filter combinations return unsupported_filter_combination instead of silently adding new index requirements.

Read a session's agent conversation GET

Lists the conversation between the team's members and the in-app Yapper agent in this session, newest first, so an integration can pick up where it left off. Each message carries its text, the asset ids of its attachments, and the name and outcome of each step the agent took or decision a member made. The agent's reasoning and its tool inputs and outputs are never returned; use GET /processes with sessionId for what was generated. A page can hold fewer than limit messages, because turns the chat does not show are skipped. A session with no conversation returns an empty list. Read-only and free. Uses the processes:read scope.