This page provides brief definitions and links to more information of terms that are used in the Cloud Endpoints documentation
- API key
- A code passed in by a client application when it calls an API. API keys identify the application or the Cloud project making the call to the API. See Why and When to use API Keys for more information on using an API key with your Cloud Endpoints API.
- A service that lets you define how users authenticate to applications. See Auth0 for more information.
- A software package that contains the libraries, frameworks, settings, etc. that an application requires to run. See What is a Container for more information.
- Cloud Endpoints Frameworks
- Google Cloud Endpoints Frameworks for App Engine standard consists of tools, libraries and capabilities that allow you to generate APIs and client libraries from an App Engine application. See About Cloud Endpoints Frameworks for more information.
- Open-source software that allows you to automate deploying applications inside software containers. See What is Docker for more information.
- Extensible Service Proxy
- The Extensible Service Proxy (ESP) is a high-performance, scalable proxy that runs in front of an OpenAPI or gRPC API backend and provides API management features such as authentication, monitoring and logging. See About Cloud Endpoints and Cloud Endpoints: Architectural Overview for more information.
- Firebase authentication
- Google's authentication service that supports end user sign-in for client applications using credentials from popular federated identity providers such as Google, Facebook, or Twitter. See Firebase authentication for more information.
- Google ID token
- A JSON Web Token (JWT) that contains the OpenID
fields needed to identify a Google user account or service account, and that
is signed by Google's authentication service,
- A high performance, open-source universal RPC framework developed by Google. In gRPC, a client application can directly call methods on a server application on a different machine as if it was a local object, making it easier to create distributed applications and services. See Cloud Endpoints for gRPC APIs for information on using gRPC with Cloud Endpoints and the gRPC website for general information.
- JSON Web Token is an open standard access token format for use in HTTP Authorization headers and URI query parameters. See Authenticating Users (OpenAPI) for information on using JWT with your Cloud Endpoints API and Introduction to JSON Web Tokens for general information.
- A command line interface for running commands against Kubernetes clusters. You
kubectlwhen deploying an API for Cloud Endpoints on a Kubernetes or Google GKE cluster. See Overview of kubectl for more information.
- Open-source software that allows you to automate the deployment, management, and scaling of containerized applications across clusters of hosts. See Kubernetes for more information.
- An open-source, high-performance HTTP server and service proxy that the Extensible Service Proxy is based on. See the NGINX Wiki for more information. For information on the Extensible Service Proxy, see About Cloud Endpoints and Cloud Endpoints: Architectural Overview.
- The Open API Initiative is an industry-wide effort to standardize the description of REST APIs. APIs that are described with the OpenAPI Specification (formerly the Swagger Specification) can be supported with common tools that create documentation, automate testing, and generate code for clients and servers. See OpenAPI Overview for more information.
- OpenAPI document
- A configuration file in either YAML or JSON format that you use to describe your API. See Swagger Basic Structure for more information.
- Swagger UI
- The Swagger UI allows anyone to try out operations that your API exposes. See Adding SwaggerUI to your project for details on adding a Swagger UI to your Cloud Endpoints API.
- The public interface of an API. An API's surface consists of the methods as well as the parameters and return types used in the methods.