We recommend that you use the latest version of this feature, which is renamed to Cloud Endpoints Frameworks for App Engine. This new version supports App Engine standard environment, provides lower latency, and has better integration with App Engine. For more details, see Migrating to 2.0.
You must define an API server that uses the API or APIs you have created. To define an API server:
-
Create a Python module, for example
main.py, and create anendpoints.api_serverobject at the top-level:Note that you provide a list of
remote.Serviceobjects to the API server. If you have an API that is is implemented in several classes, then yourServiceobject is a collection of classes as described in Creating an API Implemented with Multiple Classes.Notice that we describe using a separate module for the API server: this is not a requirement! If you are defining multiple APIs (
remote.Servicesubclasses) that are defined in multiple files, it might be preferable to have a separate module for your API Server in order to import all these class files. However, alternatively, you could just add the requiredendpoints.api_servercode shown above to the module where you define your API. If you are defining only a single API, it may be preferable to define the API server in the same file where you define your API because it doesn't need to import any other classes. -
In your
app.yamlfile, map the API server you just created to the endpoints location as follows:where
mainis the Python module you used for your API server module. Notice that the endpoints path must be/_ah/spirelative to the application. Although applications send their requests to/_ah/api, the Endpoints backend actually handles these requests at the path/_ah/spi. -
Add Endpoints to the Libraries section of
app.yaml, since the Endpoints library is not included by default:Note that you should specify the desired Endpoints library version. Currently, the only version available is the GA version, 1.0.