Repository files navigation

TL;DR: AIPs are lots of documents on how Google does APIs.

AIP stands forAPI Improvement Proposal, which is a design documentproviding high-level, concise documentation for API development. The goal isfor these documents to serve as the source of truth for API-relateddocumentation at Google and the way API teams discuss and come to consensus onAPI guidance. The program is named and styled after Python's enhancementproposals (PEPs) which have seemed to work pretty well over the years.

While much of the API-related guidance is general and spans across all thedifferent products at Google, we've found that some teams working in differentareas may have different customs, styles, or guidance. To accommodate thesehistorical differences, we've provided separate blocks of numbers for thoseareas where they might override or extend the more general guidance.

If you'renew to AIPs, check out theFrequently Asked Questions whichanswer some common questions about how AIPs work and what you need to know.

If you like what you see andwant to adopt the general AIPs for yourorganization, check out our guide onAdopting AIPs in your company. Thisguide walks you through how to start using AIPs and write your own guidancespecific to your organization.

If youhave an idea for an AIP that isn't written yet (yes, there areplenty!) check outContributing to the project to see how you can writeAIPs for others to follow.

Except as otherwise noted, the content of this repository is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensedunder theApache 2.0 License.

For the full text of each license, seeLICENSE.md. Foradditional details, see the developer.google.comSite Policies.