---
schema_version: "1"
id: 593e5ac27286c17c6f2e11ab6977193ebd581e67374b6f2d7cb1edf04379b695
title: Actionable Telematics Event Business API and Platform Events
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/ca_aeo_apis_and_platform_events.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.ca_aeo_apis_and_platform_events.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: dfb256cde921464fe15d510056e8d9cdbbc7184960213d7abd89fd834b52c6f3
description: Different methods are available to bring asset events into Salesforce and execute actions on the event. Use the Actionable Orchestration Source Event platform event to publish events or use the Orchestration Inbound Events business API to trigger events. The platform event and the business API can be easily integrated with any external system, such as telematics provider systems.
products:
  - Industry Solutions
  - Cross Cloud
release: "264"
---
# Actionable Telematics Event Business API and Platform Events

Different methods are available to bring asset events into Salesforce and execute actions on the event. Use the Actionable Orchestration Source Event platform event to publish events or use the Orchestration Inbound Events business API to trigger events. The platform event and the business API can be easily integrated with any external system, such as telematics provider systems.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Automotive Cloud, Communications Cloud, Consumer Goods, Energy and Utilities Cloud, Manufacturing Cloud, and Media Cloud. <a href="https://help.salesforce.com/s/articleView?id=xcloud.ca_editions.htm&amp;release=264.0.0&amp;type=5" title="Review the supported products and editions for Connected Assets features.">View edition availability</a>.</td></tr></tbody></table>

Here’s the process to use the platform event framework to ingest events.

- Phase 1 – Prepare Input Data: The request payload must contain the source system identifier and event type at a minimum. In addition, event subtype and event category can also be specified. For additional events data, make sure the JSON structure matches the nodes and attributes for a context definition.
- Phase 2 – Publish the Source Event: Publish the Actionable Orchestration Source Event platform event from an external system so that you can establish the connection between the external system and Salesforce. Salesforce receives all events originating in the external system after the platform event is published.
- Phase 3 – Subscribe to the Response Event: Subscribe to Actionable Orchestration Response Event to notify the external system after an action is executed for the source event. The response contains the details of the executed action, the processing status of the source event, and the error description for a failed event.

For details, see [Platform Events Developer Guide](https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_events_intro.htm).

Perform these high-level steps if you use the business API to ingest events.

- Prepare Input Data: The request payload must contain the source system identifier and event type at a minimum. In addition, event subtype and event category can also be specified. For additional events criteria, make sure the JSON structure specifies the key-value pairs for each type of detail.
- Trigger the API: Use a POST method to trigger the API that automatically invokes the actionable event orchestration framework.
- Review the Results: Review the API response, which lists the actions taken by the orchestration process for a specified event. The response contains the details of the executed action, the processing status of the source event, and the error description for a failed event.

For details, see [Orchestration Events (POST)](https://developer.salesforce.com/docs/atlas.en-us.automotive_cloud.meta/automotive_cloud/connect_resources_inbound_events.htm).