Full form: Representational State Transfer Application Programming Interface
Also known as: Representational State Transfer, REST, RESTful API
Quick Definition
An API architectural style that uses HTTP methods (GET, POST, PUT, DELETE) to interact with network resources.
REST APIs are the dominant API style for modern network management. They use standard HTTP methods: GET (read), POST (create), PUT/PATCH (update), DELETE (remove). Data is typically exchanged in JSON or XML format. Cisco platforms like DNA Center, Meraki, and vManage expose REST APIs, allowing network automation scripts and tools to configure and monitor devices programmatically.
REST APIs are stateless — each request contains all necessary information. The response status codes matter: 200 OK, 201 Created, 400 Bad Request, 401 Unauthorized, 404 Not Found, 500 Server Error.
A lightweight, human-readable data format used to exchange data between APIs and automation tools.
An architecture that separates the network control plane from the data plane, enabling centralised programmability.
APIs on an SDN controller that allow applications and management tools to communicate with the controller.
REST APIs are the dominant API style for modern network management. They use standard HTTP methods: GET (read), POST (create), PUT/PATCH (update), DELETE (remove). Data is typically exchanged in JSON or XML format. Cisco platforms like DNA Center, Meraki, and vManage expose REST APIs, allowing network automation scripts and tools to configure and monitor devices programmatically.
REST APIs are stateless — each request contains all necessary information. The response status codes matter: 200 OK, 201 Created, 400 Bad Request, 401 Unauthorized, 404 Not Found, 500 Server Error.
REST API falls under the Automation domain of the 200-301 exam. Understanding it in context with related terms like json and sdn is essential for answering scenario-based questions correctly.