<commit_before>---
title: API Blueprint
---

## API Blueprint. A powerful high-level API description language for web APIs.

API Blueprint is simple and accessible to everybody involved in the API
lifecycle. Its syntax is concise yet expressive. With API Blueprint you can
quickly design and prototype APIs to be created or document and test already
deployed mission-critical APIs.

[Tutorial](./documentation/) [Tools section](./tools.html) 

```apib
# GET /message
- Response 200 (text/plain)

        Hello World!
```

### Focused on Collaboration

API Blueprint is built to encourage dialogue and collaboration between
project stakeholders, developers and customers at any point in the API
lifecycle. At the same time, the API Blueprint tools provide the support to
achieve the goals be it API development, governance or delivery.

### Open

API Blueprint is completely open sourced under the MIT license.
Its future is [transparent and open][roadmap].
API Blueprint doesn't need a closed work group. Instead it uses the RFC
process similar to Rust language or Django Enhancement Proposal RFC processes.
<commit_msg>[Homepage] Fix links to the tutorial<commit_after>---
title: API Blueprint
---

## API Blueprint. A powerful high-level API description language for web APIs.

API Blueprint is simple and accessible to everybody involved in the API
lifecycle. Its syntax is concise yet expressive. With API Blueprint you can
quickly design and prototype APIs to be created or document and test already
deployed mission-critical APIs.

[Tutorial](/documentation/tutorial.html) [Tools section](/tools.html)

```apib
# GET /message
- Response 200 (text/plain)

        Hello World!
```

### Focused on Collaboration

API Blueprint is built to encourage dialogue and collaboration between
project stakeholders, developers and customers at any point in the API
lifecycle. At the same time, the API Blueprint tools provide the support to
achieve the goals be it API development, governance or delivery.

### Open

API Blueprint is completely open sourced under the MIT license.
Its future is [transparent and open][roadmap].
API Blueprint doesn't need a closed work group. Instead it uses the RFC
process similar to Rust language or Django Enhancement Proposal RFC processes.

{'fraction_non_alphanumeric': 0.05851297844258689, 'fraction_numerical': 0.0026396832380114386, 'mean_word_length': 4.440191387559809, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2797426', 'n_tokens_mistral': 598, 'n_tokens_neox': 540, 'n_words': 313}