---
schema_version: "1"
id: b1832123aa1f2cbea9e9c996f98b986e91d54a24aee227eec3124814f57b27cd
title: Vehicle Telematics Business API and Platform Events
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/auto_aeo_componentsbusiness_api_and_platform_events.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.auto_aeo_componentsbusiness_api_and_platform_events.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: ef9ca7f6e9cac2722732d69fbf3a7f631a35fbf86e028042d1aa8904230bd54c
description: There are different methods to bring telematics events into Automotive Cloud 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 telematics provider system.
products:
  - Automotive
release: "264"
---
# Vehicle Telematics Business API and Platform Events

There are different methods to bring telematics events into Automotive Cloud 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 telematics provider system.

### 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: <strong>Enterprise</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</td></tr></tbody></table>

Here’s the process to use the platform event framework to ingest events. For details, see [Platform Events Developer Guide](https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_events_intro.htm)

- 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 app so that you can establish the connection between the telematics provider and Salesforce. Salesforce receives all events originating in the telematics system after the platform event is published.
- Phase 3 - Subscribe to the Response Event: Subscribe to the Actionable Orchestration Response Event platform event so that the external system is notified 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.

Here are the high-level steps that must be performed if you use the business API to ingest events. For details, see [Orchestration Events (POST)](https://developer.salesforce.com/docs/atlas.en-us.automotive_cloud.meta/automotive_cloud/connect_resources_inbound_events.htm)

- 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 you want to specify.
- Trigger the API: Use a POST method to trigger the API that automatically invokes the actionable event orchestration framework.
- Review the Results: Review the response of the API that 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.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-automotive-264-0-0-production-enus/55098325-b838-4fed-9e79-8cfa2d7b33a3/images/icon_note.png)

Note While preparing the input data, if you edit your input mappings for a context definition, make sure your input payload's event data has the input mapping names that you provided. It should not have the node names. Also, make sure to provide values for all the input mappings for the attributes.

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-automotive-264-0-0-production-enus/55098325-b838-4fed-9e79-8cfa2d7b33a3/images/icon_example.png)

Example

For example, if the input mapping for an Event node is Asset, the input payload should look like this:

```
{

 "sourceSystemIdentifier": "5566315809",

 "type": "WorkshopEvent",

 "eventData": "{"Asset":[{"assetId":"02i5Y00000ZJ5zPQAT","signals":[{"thresholds":[{"lower":1200,"upper":1900}]}]}]}"

}
```