Page Comparison

{
  "endpoints": {							
    "getAllCountries": {
      "route": {
        "httpMethod": "GET",
        "segments": {
          "Countries": {
            "isLiteral": true,
            "type": "string"
          }
        }
      },
      "inputEntityDefinition": null,
      "outputEntityDefinition": {
        "isCollection": true,
        "name": "Country",
        "fields": {
          "id": {
            "type": "long"
          },
          "country": {
            "type": "string"
          },
          "ISOCode": {
            "type": "string"
          }
        }
      },
      "businessLogic": {
        "allCountriesRetrieval": {
          "executionType": "processFlow",
          "processFlowProperties": {
            "processFlowName": "Execute Data Object",
            "processFlowParameters": {
              "DataObjectName": "spGeteBusiness6_0CountryList"
            }
          }
        }
      },
      "security": {
        "AllowAnonymous": {
          "type": "AllowAnonymous"
        }
      }
    }
  }
}

 
All Endpoint.json files have a single 'endpoints' block.  Its children are the end points we're defining.  
Here we have one endpoint named 'getAllCountries' and we see its 5 parts:  route, input, output, business logic and security.  
 
 
 
 
 
 
 
 
This end point accepts no input.  
 
The output for this end point is a collection of objects with fields for the id, country, and ISO code.  
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
This end point executes a single process flow that calls a database object.  The output from that process flow will be translated into 
the output entity definition.
 
 
 
 
 
 
 
 
 
Anyone is allowed to call this end point.  By default all end points require authentication.