---
sourceDocument: Brazil Sales Customer Relationship Management
sourceDocumentLink: https://www.servicenow.com/docs/r/order-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Sales Customer Relationship Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# CRM API Core

# CRM API Core {#ariaid-title1}

Release version: Brazil  
Updated September 28, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Enables seamless tracking and management of Sales Customer Relationship Management workflows through structured inbound and outbound request handling, configurable flow processing, and integration with external systems.

## Overview of CRM API Core {#sales-and-services-api-core__section_qjh_ynq_wgc}

The CRM API Core (com.sn_tmt_core) plugin has three key components.{#sales-and-services-api-core__table_t1y_j4g_xgc__entry__2}

| Table | Description |
|-|-|
| [Inbound Request](https://www.servicenow.com/docs/f3Pc1YTbxJ4kMnkUU3FfAQ "Track the status of Sales CRM workflows and enable agents to track the status of any synchronous and asynchronous flows. It also supports processing dependent records sequentially to make sure that the data stays accurate and consistent.") (sn_tmt_core_inbound_queue) | Tracks the status of both synchronous and asynchronous flows. It enables agents to monitor the progress of requests and also enables sequential processing of dependent records to maintain data accuracy and consistency. It captures detailed status information for each request. For example, when an order is created from a quote, it logs a confirmation message with the order header number. It also supports archival and cleanup policies enabling organizations to cleanup records by applying different durations for successful and failed requests to optimize data management. |
| [Inbound Request Configuration](https://www.servicenow.com/docs/EJEjN9XkSiSEUQTj3bakQA "Enables you to define the configurations to determine how each flow is processed and tracked within an Inbound Request.") (sn_tmt_core_inbound_queue_config) | Defines how each flow is processed and tracked. It's a metadata table that is referenced by the Request Configuration field in the Inbound Request Table. It enables administrators to: * Configure synchronous vs asynchronous processing. * Adapt the Request Tracker across CRM flows. * Set notification types (default, custom, or none). {#sales-and-services-api-core__ul_nmr_qbh_xgc} |
| [Outbound Request](https://www.servicenow.com/docs/NxwbN9llxKOatCOLELHO_g "Initiate outbound requests to manage service orders by interacting with external Service Order Management (SOM) to facilitate end-to-end order fulfillment. This process requires specific roles and is enabled via bi-directional REST API integration with Order Management for CRM API Core.") (sn_tmt_core_outbound_request) | Facilitates outbound interactions with external Service Order Management (SOM). It supports end-to-end order fulfillment via bi-directional REST API integration and requires specific roles. |
[Table 1. CRM API Core components]

{#sales-and-services-api-core__table_t1y_j4g_xgc} {#sales-and-services-api-core__table_qp1_mdk_dhc__entry__2}

| Role | Access |
|-|-|
| sn_tmt_core.admin | Create, read, update, delete, report_view, and report_on |
| sn_tmt_core.viewer | report_view, report_on, and read |
[Table 2. Roles and access]

{#sales-and-services-api-core__table_qp1_mdk_dhc}
**Related concepts**   

* [Using lead-to-cash foundation applications](https://www.servicenow.com/docs/aEtZF1aM3DnekYUMEEV49w "Learn how to use lead-to-cash foundation applications.")
* [Lead-to-cash foundation reference](https://www.servicenow.com/docs/itO5lqJabv0cb3g02VcaAw "Reference for lead-to-cash foundation applications.")