curl --request POST \
--url https://api.messaging.phonovation.com/ccaas/1/conversations/{conversationId}/events \
--header 'Authorization: <api-key>' \
--header 'Content-Type: application/json' \
--data '
{
"from": "03dff63b-6100-44a9-b563-8fbc0295ec77",
"to": "urn:urnId",
"channel": "APPLE_BUSINESS_CHAT",
"type": "TYPING_STARTED"
}
'Send a conversation event
Use this endpoint to send an event to a conversation. E.g. indication when typing started or ended.More info
Required scope: Enable one of: conversations:manage.
curl --request POST \
--url https://api.messaging.phonovation.com/ccaas/1/conversations/{conversationId}/events \
--header 'Authorization: <api-key>' \
--header 'Content-Type: application/json' \
--data '
{
"from": "03dff63b-6100-44a9-b563-8fbc0295ec77",
"to": "urn:urnId",
"channel": "APPLE_BUSINESS_CHAT",
"type": "TYPING_STARTED"
}
'Authorizations
This is the most secure authorization type and the one with the most flexibility.
API keys can be generated by calling the dedicated API method. Furthermore, API keys can have a limited scope and cover only some API methods. Lastly, they can be revoked at any time. This range of possibilities makes API keys well suited for separating the API access rights across multiple applications or use cases. Finally, the loss of an API key is easily manageable.
You can manage your API keys from GUI, or programmatically with dedicated API.
API key Authorization header example:
Authorization: App 003026bbc133714df1834b8638bb496e-8f4b3d9a-e931-478d-a994-28a725159ab9
Path Parameters
Id of the conversation to set event for.
Body
Sender Id.
1Destination Id.
1Event type.
TYPING_STARTED, TYPING_STOPPED Channel where the event will be sent.
LIVE_CHAT, APPLE_BUSINESS_CHAT, WHATSAPP, RCS Response
OK