Amazon Connect Participant Service

Name: Amazon Connect Participant Service API
Brand: Amazon Connect Participant Service
Availability: InStock

★ Only Publicly Available SpecCommunicationsChat MessagingAWS Signature v4 (HMAC)8 EndpointsREST

For Agents

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

Quickstart

Get started with Amazon Connect Participant Service in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"send a chat message as a Connect participant"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Amazon Connect Participant Service API.

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

GET STARTED

Start building with Amazon Connect Participant Service API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for Amazon Connect Participant Service, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Amazon Connect Participant Service API for, with concrete tasks.

★ 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.

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.

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.

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.

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

Key Endpoints

8 endpoints — jentic publishes the only available openapi specification for amazon connect participant service, keeping it validated and agent-ready.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

AWS SigV4 (HMAC) credentials for the Amazon Connect Participant Service are stored encrypted in the Jentic vault. Agents receive scoped, short-lived access via Jentic's MAXsystem rather than holding the raw AWS access key ID and secret access key in their context.

Intent-based discovery

Agents search Jentic with intents like 'send a chat message as a Connect participant' and Jentic returns the matching Amazon Connect Participant Service operation with its input schema, so the agent can call the correct endpoint without browsing the AWS service reference.

Time to first call

Direct integration: 2-4 days for SigV4 request signing, IAM policy setup, and error handling across Amazon Connect Participant Service operations. Through Jentic: under 1 hour - search by intent, load the schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Amazon Connect

The agent and instance side that issues participant tokens.

Use Connect to start the chat and issue the participant token; use Connect Participant Service to drive the customer side.

Alternative

Twilio Conversations

Twilio's multi-party conversation API for SMS, WhatsApp, and chat.

Choose Twilio Conversations for cross-channel messaging beyond Connect's web/mobile chat scope.

Alternative

Sendbird Chat

Hosted in-app chat infrastructure with rich client SDKs.

Choose Sendbird when chat is a product feature rather than a contact center channel.

FAQs

Specific to using Amazon Connect Participant Service API through Jentic.

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 at https://app.jentic.com/sign-up.

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.