Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

New API Blueprint Format Basics post published.

  • Loading branch information...
commit a39fc9bd703861e8b82ef5875d316fd73d48086c 1 parent aceec5e
@zdne zdne authored
View
5 ...-02-19-New-API-Blueprint-Format-Basics.md → ...-02-21-New-API-Blueprint-Format-Basics.md
@@ -2,9 +2,8 @@
title: New API Blueprint Format Basics
excerpt: Discussing basic features of the New API Blueprint Format – Markdown, API endpoints, multiple requests and responses and commenting on parameters.
layout: post
-date: 2013-02-20 09:00:00 +1000
+date: 2013-02-21 09:00:00 +1000
author: zdenek
-published: false
---
This is the second article in the series about upcoming API Blueprint format changes. As promised [earlier](http://blog.apiary.io/2013/01/27/New-API-Blueprint-Format/) I will continue to introduce changes to the API Blueprint Format. Today we will discuss the basics of the New API Blueprint Format upon which we will later build.
@@ -21,7 +20,7 @@ In an API Blueprint, an API endpoint is defined as a Markdown header with an opt
API Endpoint structure:
-![API Endpoint Structure](/images/2013-02-19-API-endpoint.png)
+![API Endpoint Structure](/images/2013-02-21-API-endpoint.png)
For example:
View
0  images/2013-02-19-API-endpoint.png → images/2013-02-21-API-endpoint.png
File renamed without changes
Please sign in to comment.
Something went wrong with that request. Please try again.