2.0 Understanding and Using APIs

Question 1

2.1: what are 5 common HTTP request methods

Answer 1

Get
Post
Put (U for update)
Delete
Patch (A for append)

Question 2

2.4: Response codes: 100’s

Answer 2

Informational

Question 3

2.4: Response codes: 300’s

Answer 3

Redirect

Question 4

2.4: Response codes: 200’s

Answer 4

Success

Question 5

2.4: Response codes: 500’s

Answer 5

Server Errors

Question 6

2.4: Response codes: 400’s

Answer 6

Error

Question 7

2.4 Response code 403

Answer 7

You are not authorized to view this page (HTTP Error 403 - Forbidden)

Question 8

2.4: Response code 404

Answer 8

The page cannot be found (HTTP Error 404 - File not found)

Question 9

2.4: Response code 429

Answer 9

The HTTP return code of 429 indicates that the user has sent too many requests in a given amount of time. Intended for use with rate-limiting schemes.

Question 10

2.1: what is the difference between PUT, POST, and PATCH

Answer 10

POST - Submits data to a specific destination
PUT - Replaces completly data at a specific destination
PATCH -makes a partial update on a resource

Question 11

2.2 Describe common usage patterns related to webhooks

Answer 11

Webhooks set up on a host to push data to an API when certain events trigger it.

Example: At certain points in an Amazon order the webhooks will send data to the customer portal API to update order status

Question 12

2.3 Identify the 6 constraints when consuming APIs (REST)

Answer 12

1. Client-Server
2. Stateless
3. Cache
4. Uniform Interface
5. Layered System
6. Code-On-Demand (optional)

Question 13

2.3: What does the REST API restraint “Stateless” mean?

Answer 13

The server will not store anything about the last HTTP request from a client. Each request will be treated as new.

Question 14

2.3: What does the REST API restraint “Uniform Interface” mean?

Answer 14

ses the same protocols all the time. Always HTTPS or only HTTP for example.

Question 15

2.6 Identify the parts of an HTTP response: response code

Answer 15

The code is located in the first lines, optionally it will have text beside it.

Question 16

2.6 Identify the parts of an HTTP response: headers

Answer 16

These are all Key:Value Pairs

Question 17

2.6 Identify the parts of an HTTP response: body

Answer 17

Located after the headers. The body contains the payload. There is a blank line in between the headers and the body.

Question 18

2.7 Utilize common API authentication mechanisms: API keys

Answer 18

An API key is a predetermined string that is passed from the client to the server. Anyone with this key can access the API in question.

Question 19

2.7: What are the three different ways to pass API keys?

Answer 19

String-Based: You add ?examplekey123 to each API calls URI.

Request header: In the header you define the key. Example: X-API-Key: abcdef1234

Cookies: same as a Request header besides the name of the key. Example: Cookie: abcdef1234

Question 20

2.7 Utilize common API authentication mechanisms: Basic

Answer 20

Basic calls for username password base 64 encoded and is not secure by default, use https with it to assist. Password is sent back and forth with each request.

Question 21

2.7 Utilize common API authentication mechanisms: custom token

Answer 21

The user authenticates once, the server authenticates and then sends a cryptologically signed token back to the user (JWT in most cases) and then the user can use the token to authenticate from then on.

Question 22

2.7 What is a JWT and what two componets is it comprised of?

Answer 22

JavaScript Web Tokens are the most popular form of token used today.

JWT = {JSON} + Cryptologic Signature

Question 23

2.8 Compare common API styles REST

Answer 23

1. Uniform Interface - Example: all calls have to use same tech, ie HTTP only or HTTPS
2. Client-Server: The client and server cannot be on the same software, they need to be separate applications even if on the same computer.
3. Statelessness: Every API call has to contain everything required to complete the requested operation

Question 24

2.8 Compare common API styles RPC

Answer 24

RPC is a protocol that allows a program to execute code on a remote server as if it were a local procedure call. Unlike REST, which operates on resources, RPC emphasizes direct function calls, making it simpler for specific tasks but potentially less scalable for large systems.

Question 25

2.8 Compare common API styles synchronous

Answer 25

A synchronous API requires the client to wait for the server to process a request and return a response, leading to blocking behavior. This approach is straightforward and easier to implement, but it can result in delays.

Question 27

2.8 Compare common API styles asynchronous

Answer 27

An asynchronous API enables the client to send a request and continue processing without waiting for a response, promoting non-blocking behavior. This is beneficial for performance and user experience, particularly in high-load scenarios, and sets it apart from synchronous APIs, which can hinder responsiveness.