From d4b263dd0ce3da3d0206afd1b5920b24d2b00915 Mon Sep 17 00:00:00 2001 From: Jeremy Stretch Date: Wed, 18 Sep 2019 16:41:08 -0400 Subject: [PATCH] Fixes #3439: Add a note about the Swagger API interface --- docs/api/overview.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/api/overview.md b/docs/api/overview.md index e74a12371..5dd8c178e 100644 --- a/docs/api/overview.md +++ b/docs/api/overview.md @@ -1,5 +1,3 @@ -NetBox v2.0 and later includes a full-featured REST API that allows its data model to be read and manipulated externally. - # What is a REST API? REST stands for [representational state transfer](https://en.wikipedia.org/wiki/Representational_state_transfer). It's a particular type of API which employs HTTP to create, retrieve, update, and delete objects from a database. (This set of operations is commonly referred to as CRUD.) Each type of operation is associated with a particular HTTP verb: @@ -34,6 +32,10 @@ $ curl -s http://localhost:8000/api/ipam/ip-addresses/2954/ | jq '.' Each attribute of the NetBox object is expressed as a field in the dictionary. Fields may include their own nested objects, as in the case of the `status` field above. Every object includes a primary key named `id` which uniquely identifies it in the database. +# Interactive Documentation + +Comprehensive, interactive documentation of all API endpoints is available on a running NetBox instance at `/api/docs/`. This interface provides a convenient sandbox for researching and experimenting with NetBox's various API endpoints and different request types. + # URL Hierarchy NetBox's entire API is housed under the API root at `https:///api/`. The URL structure is divided at the root level by application: circuits, DCIM, extras, IPAM, secrets, and tenancy. Within each application, each model has its own path. For example, the provider and circuit objects are located under the "circuits" application: