{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":1316,"path":"api-reference/web-services/r_RESTMessageElements.md","title":"REST message elements","bundle":null,"doc_type":null,"release":"australia","body":"\n# REST message elements\n\nAn outbound REST message is composed of several elements, such as the endpoint and HTTP methods.\n\nA REST message contains the following elements:\n\n<table id=\"table_ml1_pt1_5s\"><thead><tr><th>\n\nElement\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nEndpoint\n\n</td><td>\n\nThe endpoint is the URL of the data to be retrieved, updated, or deleted. Every REST message must specify an endpoint.\n\n</td></tr><tr><td>\n\nHeaders\n\n</td><td>\n\nHTTP headers in REST messages contain information about the request, such as the desired response format. A REST message may specify any number of headers.\n\n</td></tr><tr><td>\n\nAuthentication settings\n\n</td><td>\n\nAuthentication settings include which type of authentication to use, such as basic auth or OAuth, as well as the credentials to use.\n\n</td></tr><tr><td>\n\nHTTP methods\n\n</td><td>\n\nHTTP methods, such as GET, POST, or DELETE interact with the data at the endpoint. You can optionally override the parent REST message configuration in each HTTP method such as by specifying a different endpoint, authentication credentials, or headers.\n\n HTTP methods that send content, such as POST, include a message body detailing this content.\n\n A REST message may specify multiple HTTP methods. When sending a REST message, such as through a workflow activity or script, you must specify which HTTP method to use.\n\n</td></tr></tbody>\n</table>**Parent Topic:**[Outbound REST web service](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/api-reference/web-services/c_OutboundRESTWebService.md)\n\n"}}