canonical: https://jentic.com/apis/amazonaws.com/aws-connectparticipant

# AWS Amazon Connect Participant Service

Jentic publishes the only available OpenAPI specification for Amazon Connect Participant Service, keeping it validated and agent-ready. Amazon Connect Participant Service is the customer-side API for Amazon Connect chat sessions. Once a chat is started through Amazon Connect, the participant exchanges a participant token for a connection, then sends messages, posts events such as typing indicators, and uploads attachments through this API. It powers the customer half of every Amazon Connect chat experience.

## For AI agents

Connect a customer-side participant to an Amazon Connect chat session, send and receive messages, post events, and upload attachments.

## Scope

Does not handle voice, SMS, or starting chat sessions - use Amazon Connect to start the chat, then this API for the customer-side connection only.

## Capabilities

- Establish a participant connection to a Connect chat using a participant token
- Send chat messages and post participant events such as typing and read receipts
- Retrieve the chat transcript for a session
- Upload attachments to a chat through StartAttachmentUpload and CompleteAttachmentUpload
- Disconnect a participant from an active chat
- Cancel an in-progress attachment upload

## Use cases

### Customer-Side Web Chat Widget

Companies embed a chat widget on their website that talks to Amazon Connect on the customer's behalf. The widget exchanges a participant token (issued by StartChatContact on the agent side) for a connection via CreateParticipantConnection, then uses SendMessage and SendEvent to drive the conversation. Integration takes one to two days for a polished widget.

Example prompt: Call CreateParticipantConnection with a participant token, then SendMessage with ContentType=text/plain and a greeting.

### Mobile-App Chat Integration

Mobile apps embed Connect chat directly so customers can reach support without leaving the app. Connect Participant Service handles the connection, message stream, and attachments such as receipts or screenshots, while the agent side uses Connect itself. Push of new messages is via a websocket negotiated through CreateParticipantConnection.

Example prompt: Call StartAttachmentUpload for a JPEG, upload the bytes to the returned URL, then CompleteAttachmentUpload to attach it to the chat.

### Transcript Retrieval and Disconnection

When a chat ends, applications need to fetch the transcript for storage, search, and analytics, and to disconnect the participant cleanly. GetTranscript returns paginated message and event history, and DisconnectParticipant ends the participant's session.

Example prompt: Call GetTranscript with a ConnectionToken, page through the results, then call DisconnectParticipant to end the session.

### Agent-Bridged Chat Operations

An AI agent operating as a customer-side participant can drive automated chat flows for testing, monitoring, or self-service experimentation. Through Jentic, the agent exchanges the token, sends messages, and inspects transcripts without managing the SigV4 signing required for every Participant Service call.

Example prompt: Use CreateParticipantConnection to obtain a ConnectionToken, send a series of test messages with SendMessage, then GetTranscript to verify they were received.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /participant/connection#X-Amz-Bearer | Create a participant connection from a participant token |
| POST | /participant/message#X-Amz-Bearer | Send a chat message |
| POST | /participant/event#X-Amz-Bearer | Send a chat event such as a typing indicator |
| POST | /participant/transcript#X-Amz-Bearer | Retrieve the chat transcript |
| POST | /participant/start-attachment-upload#X-Amz-Bearer | Begin uploading an attachment |
| POST | /participant/complete-attachment-upload#X-Amz-Bearer | Finalize an attachment upload |
| POST | /participant/disconnect#X-Amz-Bearer | Disconnect the participant |

## Key resources

- **ParticipantConnection** — Establish and manage a participant's connection to an active chat using CreateParticipantConnection.
- **Message** — Send chat messages and events with SendMessage and SendEvent.
- **Transcript** — Retrieve the message and event history of a chat with GetTranscript.
- **Attachment** — Upload, complete, and cancel attachments via StartAttachmentUpload, CompleteAttachmentUpload, and GetAttachment.

## Why Jentic

- **Setup:** Wiring the Amazon Connect Participant Service by hand means implementing AWS Signature v4 request signing, resolving the regional participant.connect host, and passing the participant token as an X-Amz-Bearer header on every call. Through Jentic you install once, import Amazon Connect Participant Service from the API Directory, store the AWS credentials once, and your agent calls it.
- **Permission scoping:** This API exposes participant operations like sending a message, posting an event, and retrieving the transcript, and the chat is identified by the participant token rather than a resource id in the URL path. Limit the agent to the operations it needs, such as CreateParticipantConnection and SendMessage, so operations like DisconnectParticipant are not included unless you add them.
- **Credential handling:** Your AWS credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'send a chat message as a Connect participant' or 'retrieve the chat transcript', and Jentic returns the matching Amazon Connect Participant Service operation with its input schema so the agent calls the right endpoint without browsing the AWS service reference.

## Related APIs

- **Amazon Connect** — The agent and instance side that issues participant tokens.
- **Twilio Conversations** — Twilio's multi-party conversation API for SMS, WhatsApp, and chat.
- **Sendbird Chat** — Hosted in-app chat infrastructure with rich client SDKs.

## FAQ

### Why is there no official OpenAPI spec for Amazon Connect Participant Service?

AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon Connect Participant Service via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Amazon Connect Participant Service use?

Each operation uses a participant token issued by StartChatContact and exchanged for a ConnectionToken via CreateParticipantConnection. AWS SigV4 still signs the call. Jentic stores the AWS credentials in its vault, signs the request, and threads the participant token through the X-Amz-Bearer header.

### Can I send attachments through the Amazon Connect Participant Service?

Yes. Call StartAttachmentUpload to receive a presigned upload URL, PUT the file to that URL, then call CompleteAttachmentUpload. The attachment becomes accessible via GetAttachment for any participant in the chat.

### What are the rate limits for the Amazon Connect Participant Service?

Per-account, per-region TPS limits apply, with SendMessage and SendEvent at higher TPS than GetTranscript. Plan for ThrottlingException with exponential backoff, especially when bridging multiple participants from a single backend.

### How do I send a customer-side chat message through Jentic?

Search Jentic for 'send a chat message as a Connect participant', load the SendMessage schema, and execute it with the ConnectionToken, ContentType=text/plain (or text/markdown), and the message Content. The message appears in the agent's CCP and in subsequent GetTranscript calls.

### Is the Amazon Connect Participant Service free?

There is no separate API charge - usage is billed via Amazon Connect's chat usage pricing, which charges per chat message in active sessions.

### Can I limit what my agent is allowed to do with the Amazon Connect Participant Service?

Yes. Because Jentic One is self-hosted, you set the rules for which operations and credentials your agent may use, so you can grant it just the calls it needs, such as CreateParticipantConnection, SendMessage, and GetTranscript. Since the chat is identified by the participant token rather than a resource id in the URL path, scoping is done at the operation level: leave out calls like SendEvent or DisconnectParticipant unless you deliberately add them. The stored AWS credentials are injected only at execution time for the operations you allow, so the agent cannot reach past that boundary.