Mock sample for your project: NBA Stats API

Manages Apache Airflow environments on Google Cloud Platform.

Creates and manages rules that determine when a Firebase Rules-enabled service should permit a request.

Provides methods for detection, risk analysis, and de-identification of privacy-sensitive fragments in text, images, and Google Cloud Platform storage repositories.

Beyondcorp Enterprise provides identity and context aware access controls for enterprise resources and enables zero-trust access. Using the Beyondcorp Enterprise APIs, enterprises can set up multi-cloud and on-prem connectivity solutions.

Programmatically creates and manages Firebase Dynamic Links.

api.video is an API that encodes on the go to facilitate immediate playback, enhancing viewer streaming experiences across multiple devices and platforms. You can stream live or on-demand online videos within minutes.

Detects objects, explicit content, and scene changes in videos. It also specifies the region for annotation and transcribes speech to text. Supports both asynchronous API and streaming API.

Allow select enterprise partners to access, control, and manage Google and Nest devices programmatically.

Provides admission control and telemetry reporting for services integrated with Service Infrastructure.

MetaPub collects, normalizes and distributes publicly available program, episode, and piece metadata through the public radio system. Backed by ContentDepot and its data model, MetaPub allows producers to supply metadata through various methods:
MetaPub Agents that collect producer metadata by "crawling" existing public feeds (e.g. C24, BBC) or the producer's production system (e.g. ATC, ME, TED Radio Hour).
Manually enter metadata in the ContentDepot Portal on each program and episode.
Publish/push the metadata to the MetaPub upload API and execute an ingest job.
MetaPub then distributes this data to stations through an electronic program guide (EPG model)
for display on various listener devices such as smart phones, tablets, web streams, HD radios, RDBS enabled FM radios, and more. The EPG format is based on the RadioDNS specifications.
RadioDNS and MetaPub
The RadioDNS Service and Programme Information Specification (TS 102 818 v3.1.1) defines three primary documents: Service Information, Program Information, and Group Information. These documents, along with the core RadioDNS Hybrid Lookup for Radio Services Specification (TS 103 270 v1.2.1) define a system where an end listener device can dynamically discover program metadata and fetch the metadata via Internet Protocol (IP) requests. MetaPub's use of RadioDNS differs slightly in that MetaPub (a.k.a PRSS) acts as the "service provider" while the stations and related middleware act as the end devices. While this is not the primary use case of RadioDNS, the flexibility in the specification, service definitions, and DNS resolution allows this model to be easily represented.
This documentation gives a high level overview of how the RadioDNS specifications will be used by MetaPub, however it is strongly recommended that the related RadioDNS specifications be read for implementation details, definitions, and required XML schemas.
ContentDepot Drive
ContentDepot Drive (CD Drive) provides a private, per customer file storage solution similar to other cloud storage solutions such as Google Drive, Box, and Dropbox. The CD Drive is used to stage content uploads such as metadata files, images, or segment audio before associating the content with specific programs or episodes.
CD Drive content can be referenced using a URI by some operations such as synchronizing metadata. There are two possible CD Drive URI formats supported: ID and hierarchical path. The ID reference takes the form . More information about URIs can be found at Wikipedia.
Authentication
The API currently uses OAuth 2.0. Some operations require specific scopes to limit clients while the ContentDepot backend may also enforce existing user specific permissions.

TPU API provides customers with access to Google TPU technology.