Version 2 vs. Version 3 of Billie Converse API and API Endpoints

Use Cases

• Real-time chat applications

• Interactive customer service interfaces

• When immediate response is required

• Structured request/response supported

• When response time flexibility is acceptable

• Systems that can handle webhook callbacks

• Structured request/response supported

Characteristics

• Synchronous request-response

• Immediate JSON response

• Direct CSR handler processing

• Built-in conversation management

• Asynchronous processing via SQS

• Webhook callback for response delivery

• Task-based tracking with unique task IDs

• Better scalability for high volumes

Response Time

• Typical: 7- 15 seconds

• Maximum: 30 seconds (API gateway timeout)

• Immediate acknowledgment (202 status)

• Actual response via webhook: 7+ seconds

Response Pattern

Immediate in HTTP response

Webhook callback to your endpoint

Integration Complexity

Simple - standard HTTP request/response

Moderate - requires webhook endpoint

Scalability

Limited by API gateway timeout (30s)

High - queue-based processing

Error Handling

Direct error response in HTTP body

Webhook delivery with error status

Best For

Interactive UI applications

Backend system integrations

Required Infrastructure

HTTP client only

HTTP client + webhook endpoint