PAparley
Sessions

Send a message

Send a message to a session. An idle assistant starts on it right away; a working one reads it at its next step, so you can steer it mid-task. Returns the session as soon as the message is queued, with status working; get the session until its status is idle, then read the reply with GET /sessions/{id}/messages. Sessions started in Word or Outlook can only be continued there. Returns 409 SESSION_BUSY while the session is being summarized or changed, and 429 USAGE_LIMIT_REACHED when the organization has used its Parley AI allowance for the billing period.

post/sessions/{id}/messages

Request

  • Base URL
    https://api.parley.so/v1
  • URL
    https://api.parley.so/v1/sessions/{id}/messages
  • Auth
    HTTP bearer

Path parameters

idstring required

The session ID.

Request body

messagestring required

The message, up to 100,000 characters.

Response

OK

idstring required

The session ID.

titlestring nullable required

The session's title, written by Parley after the first reply unless someone named it, or null until then.

status'working' | 'idle' required

working: Parley's assistant is working, a message is waiting for it, or it is waiting on subagents it started in the background. idle: the assistant has stopped and is waiting for the next message.

origin'web' | 'word' | 'outlook' | 'automation' | 'api' required

Where the session was started: web (Parley's web app, or an email to Parley's assistant), word or outlook (the add-in), automation (an automation run), or api (the REST API, MCP, or the CLI).

urlstring uri required

Where to open the session in Parley.

createdAtstring date-time required

When the session was started.

updatedAtstring date-time required

When the session last changed, such as by a new message.

Changes

No recorded changes to this operation across all 2 revisions of this API.