Submit a Billing Care Chat Request
post
/invoke/chat
The endpoint submits a Billing Care chat request through the hosted integration route. The /chat endpoint provides an equivalent compatibility alias.
Request
Header Parameters
-
X-Session-Id: string
Specifies the existing session's ID. The response returns the active session's ID in the X-Session-Id header and the response body.
Supported Media Types
- application/json
Root Schema : schema
Type:
Show Source
object-
account_id: [
"string",
"null"
]
Specifies the optional Billing Care account reference or POID.
-
confirmed: boolean
Default Value:
falseThe service accepts this field for compatibility. The API does not support write operations. -
conversation_messages: [
"array",
"null"
]
conversation_messages
Specifies the optional legacy conversation history as [role, content] pairs.
-
message(required): string
Minimum Length:
1Specifies the customer's billing or payment question. -
operation_payload: [
"object",
"null"
]
operation_payload
Additional Properties Allowed:
trueThe service accepts this field for compatibility. The API does not support write operations. -
previous_messages: [
"array",
"null"
]
previous_messages
Specifies the optional conversation history.
-
session_id: [
"string",
"null"
]
Specifies the optional session ID. The X-Session-Id header takes precedence when the request supplies it.
-
user_role: string
Default Value:
customerThe service accepts this field for compatibility.
Nested Schema : conversation_messages
Type:
arraySpecifies the optional legacy conversation history as [role, content] pairs.
Show Source
-
Array of:
array items
Minimum Number of Items:
2Maximum Number of Items:2
Nested Schema : operation_payload
Type:
objectAdditional Properties Allowed:
trueThe service accepts this field for compatibility. The API does not support write operations.
Nested Schema : previous_messages
Type:
arraySpecifies the optional conversation history.
Show Source
Nested Schema : items
Type:
arrayMinimum Number of Items:
2Maximum Number of Items:
2Nested Schema : PreviousMessage
Type:
Show Source
object-
content(required): string
Minimum Length:
1Example:What was my previous bill? -
role(required): string
Minimum Length:
1Example:user
Security
-
bearerAuth: http
Type:
httpDescription:The deployment requires bearer authentication only when it enables IDCS authentication.
Response
200 Response
The request was completed successfully. If the system throws a runtime error, the response code 200 is returned alongside the error message in the response body. If a request asks for another account's bill details, the response body contains status: error instead of an HTTP error response.
Headers
-
X-Session-Id:
Specifies the active conversation's session ID.
Root Schema : ChatResponse
Type:
Show Source
object-
account_id: string
Specifies the account's display ID when the service resolves an account.
-
agent: string
Example:
billing_care_agent -
follow_up_questions: array
follow_up_questions
-
intent: string
Specifies the intent that the service returns in certain validation responses.
-
requested_account_id: string
Specifies the account reference that the service uses to process the request.
-
response_format: string
Allowed Values:
[ "string", "list", "table" ] -
response_text(required): string
Specifies the customer-facing answer, which always ends with the AI-generated-response disclosure.
-
session_id(required): string
-
status(required): string
Allowed Values:
[ "ok", "error" ]
Examples
401 Response
The request does not include a valid bearer token, which the deployment requires when IDCS authentication is enabled.
422 Response
The request contains an invalid body or header.
502 Response
The billing agent could not process the request.
503 Response
The billing agent is temporarily unavailable.