---
title: API release notes
description: The ServiceNow APIs enable organizations to programmatically integrate ServiceNow with other systems, automate business processes, and extend platform capabilities to create seamless, end-to-end workflows across their entire IT and business ecosystem. See the following sections for release notes by family and store release.ServiceNow APIs enable you to build custom applications and experiences. APIs were enhanced and updated in the ServiceNow Store release.ServiceNow APIs enable you to build custom applications and experiences. APIs were enhanced and updated in the ServiceNow Store release.ServiceNow APIs enable you to build custom applications and experiences. APIs were enhanced and updated in the Brazil release.ServiceNow APIs enable you to build custom applications and experiences. APIs were enhanced and updated in the ServiceNow Store release.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/release-notes/api-rn-static.html
release: brazil
topic_type: topic
last_updated: "2026-09-10"
reading_time_minutes: 9
breadcrumb: [Features and changes by product, Release notes for upgrading from Australia, Learn about the Brazil release, Brazil release notes]
---

# API release notes

The ServiceNow® APIs enable organizations to programmatically integrate ServiceNow® with other systems, automate business processes, and extend platform capabilities to create seamless, end-to-end workflows across their entire IT and business ecosystem. See the following sections for release notes by family and store release.

## About ServiceNow® APIs

-   Use server-side JavaScript APIs in scripts to change the application functionality.
-   Run client APIs whenever a client-based event occurs, such as when a form loads, a form is submitted, or a field value changes.
-   Use inbound REST APIs to interact with various ServiceNow functionalities within your application.
-   Client Next Experience APIs include client APIs compatible with the Next Experience UI.

See [API implementation and reference](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/api-implementation-reference.md) for more information.

## Activation and other requirements

-   **Activation information**

    API activation is dependent on the specific product or application where the API is required. Consult your product documentation or contact your ServiceNow® administrator to determine activation steps for your use case.


**Parent Topic:**[Features and changes by product](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/release-notes/new-features-changes.md)

## November 5, 2026

ServiceNow® APIs enable you to build custom applications and experiences. APIs were enhanced and updated in the ServiceNow Store release.

### What's changed

-   ****

<table id="table_rgg_kz3_sjc"><thead><tr><th>

Application

</th><th>

App Version

</th><th>

API type

</th><th>

API

</th><th>

Methods/Endpoints

</th></tr></thead><tbody><tr><td>

Customer Service Management

</td><td>

6.7.5

</td><td>

REST

</td><td>

[Trouble Ticket Open API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/trouble-ticket-open-api.md)

</td><td>

**Important:** Migration Notice

Starting with the November 2026 release, the Trouble Ticket API transitions scope to Telecom Service Management Core \(`sn_ind_tsm_core`\) from SD-WAN \(`sn_ind_tsm_sdwan`\). Existing `sn_ind_tsm_sdwan` endpoints remain available but are deprecated until the Denmark release.Migrate your integrations to the new endpoints before the Denmark release to avoid disruption. See Trouble Ticket Open API documentation for timeline and migration guidance.

</td></tr><tr><td>

Customer Service Management

</td><td>

6.7.5

</td><td>

Server

</td><td>

[TroubleTicketNotificationUtilOOB - Scoped](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/server-api-reference/TroubleTicketNotifScopedAPI.md)

</td><td>

Starting with the November 2026 release, Trouble Ticket APIs transitions scope from `sn_ind_tsm_sdwan` to `sn_ind_tsm_core`. An automatic upgrade is planned for the December release for existing customers whose instances use S-DWAN.

</td></tr><tr><td>

Customer Service Management

</td><td>

1.8.0

</td><td>

REST

</td><td>



</td><td>

POST /openframe/voice-interaction endpoint now returns an existing callback interaction instead of creating a new one when the first item in the **relatedRecords** array is an interaction record. This helps avoid duplicate interaction records when an agent calls a customer back from a callback interaction. The response includes the sys\_id and number of the existing interaction.

</td></tr></tbody>
</table>
### What's deprecated or removed

-   **Trouble Ticket Open API**

    [Trouble Ticket Open API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/trouble-ticket-open-api.md) endpoints under the `sn_ind_tsm_sdwan` scope are deprecated but remain available until the Denmark release, at which point they will be officially removed and inaccessible. Endpoints use a new `sn_ind_tsm_core` scope as of the November 2026 release. See Trouble Ticket documentation for migration guidance and timeline information.


## October 2026

ServiceNow® APIs enable you to build custom applications and experiences. APIs were enhanced and updated in the ServiceNow Store release.

### What's new

-   ****

    |Application|App Version|API type|API|Methods/Endpoints|
    |-----------|-----------|--------|---|-----------------|
    |Mobile SDK Libraries - Android|2.26.0|Mobile SDK|[NowChatConfiguration class - Android](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/cllent-mobile-api-reference/NowChatOptionsAndroid.md)|VoiceInputButton\(\)|
    |Mobile SDK Libraries - iOS|2.26.0|Mobile SDK|[NowChatConfiguration class - iOS](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/cllent-mobile-api-reference/NowChatOptionsiOS.md)|VoiceInputButton\(\)|
    |Zero Copy Connector for ERP \(com.snc.sn\_erp\_integration\)|10.6.0|Server|[sn\_erp\_integration API - Scoped, Global](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/server-api-reference/sn_erp_integrationBothAPI.md)|getRowCount\(\)|


### What's changed

-   ****

<table id="table_rgg_kz3_sjc"><thead><tr><th>

Application

</th><th>

App Version

</th><th>

API type

</th><th>

API

</th><th>

Methods/Endpoints

</th></tr></thead><tbody><tr><td>

Universal MCP Client

</td><td>

1.1.3

</td><td>

Server

</td><td>

[MCPClient - Scoped](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/server-api-reference/MCPClientAPI.md)

</td><td>

A new parameter **caller\_product** is added to specify the scope name of the application making the API call. This parameter is required for the following methods.-   getServers\(\)
-   getToolInfo\(\)
-   invokeTool\(\)
-   listTools\(\)


</td></tr><tr><td>

Mobile SDK Libraries - Android

</td><td>

2.26.0

</td><td>

Mobile SDK

</td><td>

[NowChatConfiguration class - Android](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/cllent-mobile-api-reference/NowChatOptionsAndroid.md)

</td><td>

New optional parameters added to UIConfiguration\(\).-   **hideServiceNowInProductBranding**: Show or hide ServiceNow branding in Virtual Agent.
-   **voiceInputButton**: Show or hide the speech-to-text microphone button in the text input bar.


</td></tr><tr><td>

Mobile SDK Libraries - iOS

</td><td>

2.26.0

</td><td>

Mobile SDK

</td><td>

[NowChatConfiguration class - iOS](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/cllent-mobile-api-reference/NowChatOptionsiOS.md)

</td><td>

New optional parameters added to UIConfiguration\(\).-   **hideBranding**: Show or hide ServiceNow branding in Virtual Agent.
-   **voiceInputButton**: Show or hide the speech-to-text microphone button in the text input bar.


</td></tr><tr><td>

Order Management for Telecommunications and Media

</td><td>

15.0.4

</td><td>

REST

</td><td>

[Product Order Open API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/tmf622_product_ordering-api.md)

</td><td>

The PATCH `/sn_ind_tmt_orm/order/productOrder/{id}` endpoint now accepts the V3 `relatedParty` item shape \(`role`/`@type`/`partyOrPartyRole`\). PATCH supports only the reference pattern for both V2 and V3 versions of the API.

</td></tr><tr><td>

Telecommunications Service Management

</td><td>

8.0.3

</td><td>

REST

</td><td>

[Product Inventory Open API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/product-inventory-open-api.md)

</td><td>

In the GET /product and GET /\{id\} endpoints, the `productCharacteristic.valueType` field now supports a new `sn_prd_invt.enableseamlessvaluetype` system property that, when enabled, returns the same backend value format the Product Order API already uses, allowing consistent characteristic value types across both APIs.

</td></tr><tr><td>

Omnichannel Callback for Customer Service Management \(sn\_callback\)

</td><td>

1.8.3

</td><td>

REST

</td><td>

[Voice Interaction Resource API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/voice-interaction-resource-api.md)

</td><td>

The `POST /api/now/openframe/voice-interaction` endpoint now prevents duplicate interactions by reusing existing work-in-progress callbacks when an agent clicks to call from the workspace. The system checks for WIP interactions with matching `inbound_id` and parties before creating a new record, and accepts a new `relatedRecords` objecy to pass callback context via `context_document` and `context_table` fields.

</td></tr></tbody>
</table>
## Brazil Early Availability

ServiceNow® APIs enable you to build custom applications and experiences. APIs were enhanced and updated in the Brazil release.

### What's new

-   ****

<table id="table_djq_2qv_bkc"><thead><tr><th>

Application

</th><th>

API type

</th><th>

API

</th><th>

Methods/Endpoints

</th></tr></thead><tbody><tr><td>

Developer Sandboxes

</td><td>

REST

</td><td>

[Developer Sandbox Management API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/developer-sandbox-management-api.md)

</td><td>

Programmatically create, list, retrieve, and destroy isolated development environments within a ServiceNow® instance.-   DELETE /dsbName
-   GET /operationId
-   GET /sandboxes
-   GET /sysId
-   POST /sandboxes


</td></tr><tr><td>

Stream Connect

</td><td>

REST

</td><td>

[Schema Registry API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/schema_registry-api.md)

</td><td>

Retrieve Avro schemas along with their subject and version history.-   GET /schemas
-   GET /schemas/ids/\{id\}
-   GET /schemas/ids/\{id\}/schema
-   GET /schemas/ids/\{id\}/subjects
-   GET /schemas/ids/\{id\}/versions
-   GET /subjects
-   GET /subjects/\{subject\}/versions
-   GET /subjects/\{subject\}/versions/\{version\}
-   GET /subjects/\{subject\}/versions/\{version\}/schema


</td></tr><tr><td>

Sales Cart

</td><td>

REST

</td><td>

[Sales Cart REST API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/sales-cart-api.md)

</td><td>

Programmatically create, read, update, and submit a sales cart and its line items, or remove a cart or line item entirely.-   POST /sales\_cart
-   PATCH /v1/sales\_cart
-   GET /v1/sales\_cart
-   GET /sales\_cart/\{cart\_id\}
-   GET /sales\_cart/\{cartId\}/line-item/\{lineItemId\}
-   POST /sales\_cart/\{cart\_id\}/submitorder
-   DELETE /sales\_cart/\{cart\_id\}
-   DELETE /sales\_cart/\{cartId\}/line-item/\{lineItemId\}


</td></tr><tr><td>

Platform \(Glide\)

</td><td>

Mobile Scripting

</td><td>

-   [MobileGlideDate - Scoped](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/MobileGlideDateScopedAPI.md)
-   [MobileGlideDateTime - Scoped](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/MobileGlideDateTimeScopedAPI.md)
-   [MobileGlideElement - Scoped](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/MobileGlideElementScopedAPI.md)
-   [MobileGlideRecord - Scoped](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/MobileGlideRecordScopedAPI.md)
-   [MobileGlideSystem - Scoped](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/MobileGlideSystemScopedAPI.md)
-   [MobileGlideTime - Scoped](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/MobileGlideTimeScopedAPI.md)
-   [MobileGlideUser - Scoped](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/MobileGlideUserScopedAPI.md)
-   [MobileScripts - Scoped](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/MobileScriptsScopedAPI.md)


</td><td>

The Mobile Offline Scripting APIs introduce a set of scripting classes in the `sn_mobile_scripting` namespace that can run against data stored on a user's device. These classes query and modify records, read and write field values, and evaluate dates and times, so button conditions and write-back actions continue to work while the mobile app is offline. Because mobile scripts are a subset of the scripting capabilities available in the browser, the same script runs on the instance without modification when connectivity is available.

</td></tr><tr><td>

Process Mining

</td><td>

Server

</td><td>

[ProcessMiningIntegrationAPI - Scoped](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/server-api-reference/ProcessMiningIntAPIScoped.md)

</td><td>

createProjectFromApi\(\): Create a process mining project and retrieve project data.

</td></tr><tr><td>

Unified Secrets Gateway

</td><td>

Server

</td><td>

[SecretsAPI - Scoped](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/server-api-reference/SecretsAPI.md)

</td><td>

Provides an entry point for delivering credentials to a MID Server without requiring the caller to know the underlying storage mechanism.Available methods:

-   getSecret\(\)
-   getSecrets\(\)


</td></tr><tr><td>

AI Search

</td><td>

REST

</td><td>

[Custom Connector Gateway API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/custom-connector-gateway-api.md)

</td><td>

Push documents and user principals from a connector in your own environment into AI Search, so you can index sources that ServiceNow can't reach.-   POST /xcc-ingest \(ADDDOCUMENT\)
-   POST /xcc-ingest \(ADDPRINCIPAL\)
-   POST /xcc-ingest \(DELETEALLDOCUMENTS\)
-   POST /xcc-ingest \(DELETEALLPRINCIPALS\)
-   POST /xcc-ingest \(DELETEBYQUERY\)
-   POST /xcc-ingest \(DELETEDOCUMENT\)
-   POST /xcc-ingest \(DELETEPRINCIPAL\)


</td></tr></tbody>
</table>
### What's changed

-   ****

    |Application|API type|API|Endpoints|
    |-----------|--------|---|---------|
    |Virtual Agent and Live Agent|REST|[Virtual Agent Bot Integration API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/bot-api.md)|POST /bot/integration: The `history` parameter of the Virtual Agent Bot Integration API now supports an `attachment` type, letting the primary bot include files that were shared earlier in the conversation when it passes chat history to Virtual Agent or Live Agent.|


### What's deprecated or removed

-   **[ProcessMiningIntegrationAPI - Scoped](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/server-api-reference/ProcessMiningIntAPIScoped.md)**

    The createProject\(\) method is deprecated. Use createProjectFromApi\(\) instead. The properties **promin.api.allow\_no\_role\_mining** and **promin.api.auto\_share\_project\_with\_creator** are also deprecated.


## September 2026

ServiceNow® APIs enable you to build custom applications and experiences. APIs were enhanced and updated in the ServiceNow Store release.

### What's new

-   ****

<table id="table_djq_2qv_bkc"><thead><tr><th>

Application

</th><th>

App Version

</th><th>

API type

</th><th>

API

</th><th>

Endpoints

</th></tr></thead><tbody><tr><td>

Telecommunications Open APIs, Order Management for Telecommunications, Media, and Technology

</td><td>

8.0.1, 15.0.0

</td><td>

REST

</td><td>

[Product Offering Qualification API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/product-offering-qualification-api.md)

</td><td>

-   POST /queryProductOfferingQualification
-   POST /checkProductOfferingQualification


</td></tr></tbody>
</table>
### What's changed

-   ****

<table id="table_rgg_kz3_sjc"><thead><tr><th>

Application

</th><th>

App Version

</th><th>

API type

</th><th>

API

</th><th>

Methods/Endpoints

</th></tr></thead><tbody><tr><td>

Workplace Calendar Synchronization

</td><td>

3.4.16

</td><td>

REST

</td><td>

[WSD Recurring Reservation API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/wsd_recur_reserv-api.md)

</td><td>

POST /create\_series: The recurringPattern parameter now uses RFC 5545 iCalendar format \(freq, dtstart, interval, byweekday, tzid, etc.\) for better timezone handling and standards compliance. **Note:** Legacy format patterns \(using repeats, options.\*, and startDate\) remain supported and continue to work without changes.

</td></tr><tr><td>

Interaction Controls Component

</td><td>

3.0.1

</td><td>

Client

</td><td>

[openFrameAPI - Client](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/c_openFrameAPI.md)

</td><td>

-   setICContext\(\): Supports supervisor monitoring controls \(coaching, monitoring, barging\), callback transfer enhancements with directTarget support, and clarified conditional logic for callback context timing.
-   subscribe\(\): Supports five new callback-related sub-actions \(callbackLeaveAndTransfer, getSearchTarget, getMoreInfo, callbackTransferInitiated, cancelCallbackTransfer\) and the openframe\_icc\_record\_opened event for manager role interaction tracking.

</td></tr><tr><td>

Product Catalog Management Core application

</td><td>

20.0.2

</td><td>

REST

</td><td>

[Product Catalog Search API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/product-catalog-search-api.md)

</td><td>

The POST /search endpoint now returns the **productOfferingFamily** field, which identifies the product offering family that each offering belongs to.

</td></tr><tr><td>

Product Catalog Management Core application

</td><td>

20.0.2

</td><td>

Server

</td><td>

[CatalogSearchAPI - Scoped, Global](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/server-api-reference/CatalogSearchAPI-scoped_global.md)

</td><td>

The getCatalogData\(\) now returns the `productOfferingFamily` field, which identifies the product offering family that each offering belongs to.

</td></tr><tr><td>

Telecommunications Open APIs, Order Management for Telecommunications, Media, and Technology

</td><td>

8.0.1, 15.0.0

</td><td>

REST

</td><td>

[Product Order Open API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/tmf622_product_ordering-api.md)

</td><td>

PATCH /productOrder/\{id\}: -   Now supports a `changeType=nonProduct` parameter to update order and line item administrative details without triggering product change workflows or state transitions.
-   Now accepts either the system ID \(`sys_id`\) or external ID \(`external_id`\) in the `productOrderItem.id` field, reducing the need for additional lookups when updating line items.
-   Supports associating payment profiles, billing accounts, and related parties \(Account, Contact, Location, and Consumer\) with product orders. This allows clients to link existing records or create new ones inline during order placement for streamlined end-to-end order workflows.
GET/LIST endpoints now support the following query parameters: `Account`, `Contact and Consumer(Related Party)`, `externalID`.

</td></tr><tr><td>

Telecommunications Open APIs, Order Management for Telecommunications, Media, and Technology

</td><td>

8.0.1, 15.0.0

</td><td>

REST

</td><td>

[Service Order Open API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/service-order-open-api.md)

</td><td>

GET/LIST endpoints now support the following query parameters: `Account`, `Contact and Consumer(Related Party)`, `externalID`, `expectedStartDate`, `CompletionDate`, `requestedStartDate`, `requestedCompletionDate`, `expectedCompletionDate`.

</td></tr><tr><td>

Telecommunications Open APIs, Order Management for Telecommunications, Media, and Technology

</td><td>

8.0.1, 15.0.0

</td><td>

REST

</td><td>

[Product Inventory Open API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/product-inventory-open-api.md)

</td><td>

GET/LIST endpoints now support the following query parameters: `Account`, `Contact` and `Consumer`\(Related Party\), `billingAccount`.

</td></tr><tr><td>

Telecommunications Open APIs, Order Management for Telecommunications, Media, and Technology

</td><td>

8.0.1, 15.0.0

</td><td>

REST

</td><td>

[Product Catalog Open API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/product-catalog-open-api.md)

</td><td>

GET/LIST endpoints now support the following query parameters: `externalID`, `isSellable`

</td></tr><tr><td>

Telecommunications Open APIs, Order Management for Telecommunications, Media, and Technology

</td><td>

8.0.1, 15.0.0

</td><td>

REST

</td><td>

[Service Test Management Open API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/service-test-management-api.md)

</td><td>

All GET and POST endpoints responses return `id` and `externalId` as distinct fields on ServiceTest and ServiceTestSpecification resources. The `id` field returns the record's `sys_id`, and `externalId` returns the value of the `external_id` column when one is set. Existing query resolution behavior is unchanged, so requests that filter on an external identifier continue to work.

</td></tr><tr><td>

Telecommunications Open APIs, Order Management for Telecommunications, Media, and Technology

</td><td>

8.0.1, 15.0.0

</td><td>

REST

</td><td>

[Product Catalog Open API](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/api-reference/product-catalog-open-api.md)

</td><td>

GET/LIST endpoints: Supports the Accept-Language request header on GET and LIST operations for retrieving translated field values, and filtering by translated name on LIST operations.

</td></tr></tbody>
</table>