Understand how to execute endpoints

Each request to execute an endpoint consists of the endpoint itself - that is, an HTTP method and a URL - as well as other information required by the endpoint being executed.

For example, the endpoint that imports configuration of keyword redirects is as follows:
POST /gsadmin/v1/cloud/redirects
You must provide the following information:
  • A message header specifying a valid OAuth access token
  • In JSON format only, a message header specifying that imported content is to be parsed as JSON. The value of this header must be: "Content-Type:application/json". This header is not used with endpoints that export or delete configuration.
  • A parameter that points to the file containing the content to be imported. This parameter is not used with endpoints that export or delete configuration.

A variety of tools and utilities exist to enable you to execute endpoints. For samples of how to execute the endpoints using the cURL command line utility, see Sample Search and Navigation REST API endpoints using cURL.