Difference between SOAP action and SOAP endpoint

vktripper
Tera Contributor

What is the difference between the SOAP action and SOAP endpoint in an outbound SOAP message? Some specific example would be helpful

1 ACCEPTED SOLUTION

When (for example) the function 'insert' is called, this function is called against the 'service address', https://demo1.service-now.com/incident.do?SOAP (You can find this URL in the last part of the WSDL).

The call itself is just a regular HTTP request, and one of the HTTP headers within that request has the name "SOAPAction", with a value of "http://www.service-now.com/incident/insert".

This action is a way for the provider to route the request the appropriate way, but has absolutely no bearing on the actual URL being used for the HTTP Request. Some other providers do not us the Soap action at all, or use a relative path, instead of a full URL.

 

So to summarize: the SOAP action isn't a 'real' URL. The URL is part of the HTTP request that's being performed on the service address.

I hope this clarifies things a bit?

View solution in original post

4 REPLIES 4

Jaspal Singh
Mega Patron
Mega Patron

Hi,

 

SOAP End point is the URL provided to the service user to invoke the services exposed by the service provider.

SOAP Action specifies which process or program is needed to be called when a request is sent by the service requester with relative path of the process/program.

 

Thanks,

Jaspal Singh

 

Hit Helpful or Correct on the impact of response.

vktripper
Tera Contributor

Why are the SOAP endpoint and SOAP action URLs different? For example here - this is from the SN wiki:

find_real_file.png

When (for example) the function 'insert' is called, this function is called against the 'service address', https://demo1.service-now.com/incident.do?SOAP (You can find this URL in the last part of the WSDL).

The call itself is just a regular HTTP request, and one of the HTTP headers within that request has the name "SOAPAction", with a value of "http://www.service-now.com/incident/insert".

This action is a way for the provider to route the request the appropriate way, but has absolutely no bearing on the actual URL being used for the HTTP Request. Some other providers do not us the Soap action at all, or use a relative path, instead of a full URL.

 

So to summarize: the SOAP action isn't a 'real' URL. The URL is part of the HTTP request that's being performed on the service address.

I hope this clarifies things a bit?

Hi,

And if the SOAP endpoint (https://server/Something/GetObjectTasks) and the SOAP action (www.someAddress.com/Object.asmx) are totally different URLs, what does that mean ?

Thank you,

Radu