---
sourceDocument: Australia Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-security

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Inbound Integrations

# New Inbound Integrations experience {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

The new inbound integration workflow in the ServiceNow Machine Identity Console provides enhanced experience for managing inbound integrations.

## Inbound integrations methods {#new-inbound-integrations__section_evy_wmq_rfc}

Inbound Integrations allow you to configure and manage external applications to access ServiceNow APIs. To view detailed usage statistics for each OAuth client, see [View Inbound API Integration Usage dashboard](https://www.servicenow.com/docs/access?context=view-inbound-api-integration-usage-dashboard&version=australia&pubname=australia-api-reference&ft:locale=en-US).

On the instance, navigate to AllMachine Identity ConsoleInbound integrationsNew integration. Choose the application connection type (grant type).

<br />

To learn more about the different grant types and how to configure them, refer to the following topics:

* [Authorization code grant](https://www.servicenow.com/docs/XdNJ~O5UabK~bGi_yAT~dQ "The OAuth authorization code grant is a secure and widely used flow for web, mobile, or desktop apps that access user data with user consent. It supports both private clients (using a client secret), and public clients (using PKCE).")
* [Client credentials grant](https://www.servicenow.com/docs/Wz5COt5OLiXTdk1xLTJ7BA "Use the OAuth client credentials grant type for back-end services or automated integrations that access ServiceNow APIs without user interaction. The client application authenticates directly using its client ID and secret, and receives an access token that represents the application itself, and not the user.")
* [Third party token grant](https://www.servicenow.com/docs/98cpdmDuRHmKChyZ2GFZug "The third party token grant enables ServiceNow to accept identity tokens from trusted external identity providers, such as Azure AD or Okta. Third party token grant provides secure, token-based access. This method supports secure access and single sign-on (SSO) in federated authentication scenarios.")
* [JSON Web token bearer grant](https://www.servicenow.com/docs/5UZxCVvkQJL2qKtiJ31k_Q "Configuring an OAuth JSON Web Token (JWT) bearer grant secures token-based authentication without user interaction. Use this flow when a client application needs secure, unattended access to ServiceNow resources, either as itself or on behalf of a user.")
* [Resource owner password credential grant](https://www.servicenow.com/docs/zv_Zk22KocGiXX_N4iSKEw "Configuring an OAuth Resource Owner Password Credential (ROPC) grant enables applications to authenticate users by directly using their credentials to obtain an access token.")
{#new-inbound-integrations__ul_txd_55b_wfc}

*[\>]: and then