Full Stack lecture 10

Question 1

Web API

Answer 1

API - Application Programming Interface

An API that can be accessed via the internet using standard web protocols, most often HTTP

Question 2

REST Architecture

Answer 2

Representational State Transfer, an architectural style, not strict.

Question 3

URI

Answer 3

Uniform Resource Identified, linked to Rest - Representational State Transfer.

Question 4

JWT

Answer 4

JSON Web Token, made up of three parts header.payload.signature

Question 5

OAuth 2.0

Answer 5

Authorization framework, widely used in APIs, without exposing credentials.

Question 6

CORS

Answer 6

Cross Origin Resource Sharing, enforced by browsers to control how web applications can make requests to a domain other than the one that served the webpage.

Question 7

Rest, Idempotency

Answer 7

Operations can be performed multiple times without changing the result. In the context of REST APIs it ensured consistency and fault tolerance. Post is the only one that’s not idempotant as multiple runs of the same command creates multiple users.

Question 9

HATEOAS

Answer 9

Hypermedia as the engine if Application State, allows clients to dynamically navigate the API via hyperlinks.

Rather than hardcoding the endpoint knowledge, the client discovers next possible actions from the data itself.

Question 10

OpenAPI ( Swagger)

Answer 10

Standard specificstion, allows you to define your API endpoints, methods, parameters, request/response structures and authentication in a machine readable YAML or JSON format.

Question 11

Postman

Answer 11

A popular API testing and collaboration platform.

Adds authorization headers, tokens, and environmental variables.

Create and save collection of requests.