Find your people. Pick a challenge. Ship something real. The CreatorCon Hackathon is coming to the Community Pavilion for one epic night. Every skill level, every role welcome. Join us on May 5th and learn more here.

REST vs SOAP

OscarN
Tera Contributor

Hey everyone, I am new to ServiceNow and learning integrations.

I get that REST uses JSON and SOAP uses XML, but not sure when SOAP is actually used in real projects since REST seems easier.

Do people still use SOAP a lot? In what cases?

Thanks!

2 ACCEPTED SOLUTIONS

abirakundu23
Giga Sage

Hi @OscarN ,
Welcome to ServiceNow Ecosystem & best wishes for learning journey !
Please go through ServiceNow official Doc : https://www.servicenow.com/docs/r/xanadu/api-reference/web-services/c_APIAnalytics.html

REST and SOAP APIs are used for Servicenow integrations.

SOAP's Features :
However, SOAP-based APIs are considered more traditional and are less commonly used in modern architectures. SOAP relies on XML, resulting in larger payloads that can be more time-consuming to process hence, less Performance  and it is more secure.

REST Features :
Modern Architecture either use REST based or Scripted API or Integration Hub or Workflow data Fabric. 
REST relies on JSON/XML/text , smaller payloads , light weight that can be less time-consuming to process hence, faster , light weight and it is less secure than SOAP.

Use Cases :

SOAP :- Use for legacy system integration on premise environment like SAP, mainframe  IBM etc. For high security require for authentication then require. WSDL based contracts. Complex financial oriented integration require

REST :- Use for Modern platform like Jira, Adobe, Docu Sign, bi directional integration b/w 2 different system or Spoke based integration. Use Table API's for CRUD operations. Implement custom base integration which is not OOB supported use scripted REST API.

Community Articles: https://www.servicenow.com/community/developer-forum/what-is-difference-between-between-rest-and-soa...

Please mark helpful and correct answer if it's worthy for you.

View solution in original post

@OscarN 

Hope you are doing good.

Did my reply answer your question?

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  10x ServiceNow MVP  ||  ServiceNow Community Leader

View solution in original post

7 REPLIES 7

pr8172510
Giga Guru

Hi @OscarN,

As per ServiceNow documentation, both REST and SOAP are supported for integrations, but they are used in different scenarios based on requirements.


 What ServiceNow Docs Say

  • REST APIs are the preferred approach for new integrations because they are:
    Lightweight, faster, and easier to work with
  • SOAP APIs are still supported for:
    Enterprise integrations and legacy systems that require strict contracts (WSDL/XML)

    When REST is used (most common)

     Recommended by ServiceNow for modern integrations:

    • JSON-based (lightweight)
    • Easy to consume (Postman, scripts, etc.)
    • Better performance
    • Widely used in:
      • Service Portal / UI Builder
      • External system integrations
      • Scripted REST APIs

    🔹 When SOAP is used

     As per docs, SOAP is used when:

    • External system only supports SOAP
    • Need WSDL-based contract
    • Strict schema validation required
    • Legacy enterprise systems (SAP, older tools)

abirakundu23
Giga Sage

Hi @OscarN ,
Welcome to ServiceNow Ecosystem & best wishes for learning journey !
Please go through ServiceNow official Doc : https://www.servicenow.com/docs/r/xanadu/api-reference/web-services/c_APIAnalytics.html

REST and SOAP APIs are used for Servicenow integrations.

SOAP's Features :
However, SOAP-based APIs are considered more traditional and are less commonly used in modern architectures. SOAP relies on XML, resulting in larger payloads that can be more time-consuming to process hence, less Performance  and it is more secure.

REST Features :
Modern Architecture either use REST based or Scripted API or Integration Hub or Workflow data Fabric. 
REST relies on JSON/XML/text , smaller payloads , light weight that can be less time-consuming to process hence, faster , light weight and it is less secure than SOAP.

Use Cases :

SOAP :- Use for legacy system integration on premise environment like SAP, mainframe  IBM etc. For high security require for authentication then require. WSDL based contracts. Complex financial oriented integration require

REST :- Use for Modern platform like Jira, Adobe, Docu Sign, bi directional integration b/w 2 different system or Spoke based integration. Use Table API's for CRUD operations. Implement custom base integration which is not OOB supported use scripted REST API.

Community Articles: https://www.servicenow.com/community/developer-forum/what-is-difference-between-between-rest-and-soa...

Please mark helpful and correct answer if it's worthy for you.

Ankur Bawiskar
Tera Patron

@OscarN 

it all depends on what 3rd party supports when it comes to integration, ServiceNow supports both.

many 3rd party integrations use REST but there are old legacy integrations which still use SOAP

Lot many customers are moving towards REST considering it's light weight and has multiple options for authentication

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  10x ServiceNow MVP  ||  ServiceNow Community Leader

@OscarN 

Hope you are doing good.

Did my reply answer your question?

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  10x ServiceNow MVP  ||  ServiceNow Community Leader