Skip to content

Instantly share code, notes, and snippets.

# API Design Patterns And Use Cases
This document lists various useful patterns for API design. We encourage API developers to consider the following patterns as a guide while designing APIs for services.
### Document Semantics, Formatting, and Naming
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC 2119](
sveryovka /
Created January 17, 2022 18:00 — forked from NetzwergX/
CopyableRecord - Impl & Tests
* MIT License
* Copyright (c) 2020 Sebastian Teumert <>
* Permission is hereby granted, free of charge, to any person obtaining a copy
* of this software and associated documentation files (the "Software"), to deal
* in the Software without restriction, including without limitation the rights
* to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
* copies of the Software, and to permit persons to whom the Software is