---
title: "Standards"
description: "Explore integration and API standards, documentation guidelines, and linting rules to ensure consistency, quality, and governance across APIs and integrations."
url: "https://sandbox.tbckong.ge/guides"
image: "https://sandbox.tbckong.ge/_og/d/c_Ocean.takumi,title_Standards,description_~RXhwbG9yZSBpbnRlZ3JhdGlvbiBhbmQgQVBJIHN0YW5kYXJkcywgZG9jdW1lbnRhdGlvbiBndWlkZWxpbmVzLCBhbmQgbGludGluZyBydWxlcyB0byBlbnN1cmUgY29uc2lzdGVuY3ksIHF1YWxpdHksIGFuZCBnb3Zlcm5hbmNlIGFjcm9zcyBBUElzIGFuZCBpbnRlZ3JhdGlvbnMu,props_eyJ0aGVtZSI6eyJtb2RlIjoibGlnaHQiLCJjb2xvcnMiOnsicHJpbWFyeSI6IiMwMGFkZWUifX19,p_Ii9ndWlkZXMi,s_3phwrTM0sd5kY8RK.png"
---

## Standards

Explore integration and API standards, documentation guidelines, and linting rules to ensure consistency, quality, and governance across APIs and integrations.

## [API & Integration Standards](#api-integration-standards)

These standards define the recommended practices, governance rules, and documentation requirements for designing, publishing, and maintaining APIs and integrations across the organization.

They help teams ensure consistency, improve developer experience, simplify integration processes, and maintain high quality standards across synchronous and asynchronous communication patterns.

## Available Standards

Integration Standard

Guidelines and standards for enterprise integrations, communication patterns, governance, and platform usage across teams.

[Open Standard](https://tbcbank.atlassian.net/wiki/spaces/EA/pages/130879439/Integration)

API Naming Standard

Naming conventions and best practices for APIs, services, resources, and endpoints to ensure consistency across platforms.

[Open Standard](https://tbcbank.atlassian.net/wiki/spaces/PLATFORMSTRIBE/pages/880476282/API+Naming+Convention)

Sync API Documentation Standard

Documentation requirements and best practices for synchronous REST APIs, including examples, schemas, and governance rules.

[Open Standard](https://tbcbank.atlassian.net/wiki/spaces/PLATFORMSTRIBE/pages/880181475/Sync+API+Documentation+Standard)

Sync API Linting Rules

Validation and linting rules for synchronous APIs to improve API quality, consistency, and governance compliance.

[Open Standard](https://tbcbank.atlassian.net/wiki/spaces/PLATFORMSTRIBE/pages/880410677/Linting+Rules)

Async API Documentation Standard

Standards and best practices for documenting asynchronous APIs, events, channels, and message contracts.

[Open Standard](https://tbcbank.atlassian.net/wiki/spaces/PLATFORMSTRIBE/pages/1024458753/Async+API+Documentation+Standard)

Async API Linting Rules

Validation and linting rules for asynchronous APIs and event-driven integrations. Documentation will be available soon.

Coming Soon

## Why Standards Matter

Why should teams follow API standards?

API standards ensure consistency across teams, simplify integrations, improve developer experience, and reduce operational and maintenance overhead.

What is the purpose of linting rules?

Linting rules automatically validate API specifications against organizational standards and best practices, helping teams identify issues early in the development lifecycle.

Do these standards apply to both sync and async APIs?

Yes. The standards cover both synchronous APIs (such as REST services) and asynchronous APIs (such as events, messaging, and streaming integrations).