---
sourceDocument: Zurich API Reference
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/api-reference

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich API Reference

ft:clusterId :

    - crapiref

bundleId :

    - crapiref

workflow :

    - Creator


---

# Mutual authentication

# Outbound REST mutual authentication {#ariaid-title1}

* Release version: Zurich
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Mutual authentication causes the web service provider and consumer to authenticate with
each other before communicating.

Mutual authentication verifies the identity of both the client and the server during an outbound REST connection.

When ServiceNow initiates an outbound REST request using mutual authentication, it presents a client certificate to the external server. The server validates the certificate and, if trusted, allows the
connection to proceed. ServiceNow similarly validates the server certificate before completing the handshake.

Mutual authentication requires a client certificate and private key stored on the ServiceNow instance, and a server certificate issued by a trusted certificate authority (CA).  
Note:  
For information about mutual authentication for inbound web services, see [Certificate-based authentication](https://www.servicenow.com/docs/access?context=certificate-based-authentication&version=zurich&pubname=zurich-platform-security&ft:locale=en-US).

For information about using a custom HTTPS protocol profile to enable mutual authentication, see [Create a protocol profile](https://www.servicenow.com/docs/GNtDLWHE5T~Uri3oVV1UZw "You can create a custom HTTPS protocol profile to specify the credentials and certificates used for outbound web services. For example, you can create a custom HTTPS protocol profile to enable mutual authentication.").