PedroGeoGISdev wiki
  • Home
  • Linux OS
    • Linux: concepts
    • Linux: basic concepts
    • Linux: Bash
    • Linux: su and sudo
    • Linux: pipes
    • Linux: File System
    • Linux: Virtual Machines

    • Linux: distros
    • Linux Distros: Ubuntu
    • Linux Distros: Mint
    • Linux Distros: Debian
    • Linux Distros: openSuse
    • Linux Distros: Manjaro
    • Linux Distros: Red Hat Enterprise

    • Linux: laboratories
    • Linux Lab#LI01-1: Choose Linux
    • Linux Lab#LI01-2: Install at least three distributions
    • Linux Lab#LI01-3: Adjust user permissions
    • Linux Lab#LI02-1: Export env user with grep and pipe
    • Linux Lab#LI03-1: Manage users and groups
    • Linux Lab#LI03-2: Manage files
    • Linux Lab#LI03-3: Manage software
    • Linux Lab#LI03-4: Manage hardware
    • Linux Lab#LI04-1: Bash scripting, qtool
    • Linux Lab#LI04-2: Bash scripts as terminal tool
    • Linux Lab#LI04-3: Distribute the terminal app

    • Linux readings
    • Linux Resources
  • DevOps
    • What is DevOps
    • DevOps: Introduction
    • DevOps: Agile and Microservices
    • Infrastructure as code (IaC)
    • Immutable Infrastructure
    • Software Lifecycle

    • Documentation
    • How to document: Quarto and Obsidian

    • Network protocols
    • Network: Basics
    • Network: Client-server
    • Network Protocols
    • Network: DNS
    • Network: API Rest
    • Network: gRPC
    • Network: Websocket
    • Network: SMTP
    • Network: Ping
    • Network: UDP
    • Network: webhook
    • Network: SOAP
    • Network: graphQL

    • Version Control
    • Git
    • GitHub
    • Idea and GitHub 2023
    • Git and GitHub 2023 CLI

    • IDEs
    • IDE: Visual Code
    • IDE: IntellJIdea

    • DevOps tools
    • Amazon Web Services AWS
    • Docker
    • Jenkins pipelines
    • Kubernetes k8s
    • Digital Ocean
    • Nagios
    • Ansible

    • DevOps Laboratories
    • Lab 1: chat App
    • Lab 2: Spring Boot AWS AEB manually
    • Lab 3: Spring Boot and AWS S3 publisher
    • Lab 4: Spring Boot Docker/Jenkins
    • Lab 5: k8s on Digital Ocean
    • Lab 6: Spring Boot AWS codecommit

    • DevOps readings
    • DevOps Resources
  • MarkUp
    • MarkUp Languages
    • Introduction Markup
    • HTML Markup
    • Markdown Markup
    • Markdown and HTML working together, good idea?

    • Quarto Markdown
    • Quarto Markdown: basics
    • Quarto Markdown: creating
    • Quarto Markdown: publishing
    • Quarto Markdown: code & data
    • Quarto Markdown: api rest call
    • Quarto Markdown: OJS Cells
    • Quarto Markdown: cheat-sheet

    • Styling: CSS
    • Cascade Style Sheet
    • Cascade Style Sheet: Box Model and Containers
    • CSS: W3.css

    • MarkUp Languages Laboratories
    • Lab#MD01-1: Create and publish by Quarto

    • MarkUp Languages readings
    • MarkUp Languages Resources
  • Java SE
    • What is Java SE
    • Java Standard Edition: Basics
    • Java Standard Edition: Principles
    • Java MOOC Helsinki
    • Java MOOC Helsinki Syllabus

    • Java Create Project
    • Java SE: Maven
    • Java SE: Create Maven Project
    • Java SE: Project push GitHub
    • Java SE: JUnit and TDD

    • Java Concepts
    • Java SE: Class and Objects
    • Java SE: Scope
    • Java SE: static modifier
    • Java SE: Coupling and DDD
    • Java SE: Packages
    • Java SE: Abstract/Interface
    • Java SE: Java 8

    • Java Principles
    • Java SE: Encapsulation
    • Java SE: Abstraction
    • Java SE: Inherence
    • Java SE: Polymorphism

    • Java Design Patterns
    • Java Patterns: UML
    • Java Patterns: Types
    • Singleton
    • Factory
    • Abstract Factory
    • Builder
    • Facade
    • Bridge
    • Decorator
    • Composite
    • Observer
    • Strategy
    • State
    • Commander

    • Java SE Laboratories
    • Lab#SE00-1: Maven Person
    • Lab#SE00-2: Maven Clinic
    • Lab#SE00-3: Library Model
    • Lab#SE00-4: Abstract/Interface Human
    • Lab#SE01-1: Maven/Gradle Person and Account
    • Lab#SE01-2: Maven/Gradle Person and Account stored in JSON
    • Lab#SE02-1: Movie/Review, Model
    • Lab#SE02-2: Movie/Review, CRUD Operations
    • Lab#SE02-3: Movie/Review, factory
    • Lab#SE02-4: Movie/Review, interactivity and coupling
    • Lab#SE02-5: Movie/Review, simulate interactivity by console
    • Lab#SE03-1: Library/Book, Core-Model
    • Lab#SE03-2: Library/Book, Sprint Zero
    • Lab#SE03-3: Library/Book, Expand Model
    • Lab#SE04-1: healthyFood Restaurant, Core Model

    • Java SE readings
    • Java SE Resources
  • Python
    • Python Basics
    • Python: Basic Concepts
    • Python: Tips
  • JavaScript
    • JavaScript Basics
    • JavaScript: Basic Concepts
    • JavaScript: Tips
  • Spring
    • Spring Legacy
    • Spring Framework
    • Spring MVC
    • Springs Servlets

    • Spring Boot Basics
    • Spring Boot: fundamentals
    • Spring Boot: create a Project
    • Spring Boot: H2 DB and Thymeleaf
    • Spring Boot: cycle

    • Spring Boot Concepts
    • Spring Boot: Dependency Injection
    • Spring Boot: Annotations
    • Spring Boot: Controller
    • Spring Boot: View
    • Spring Boot: Thymeleaf
    • Spring Boot: Vaadin Flow
    • Spring Boot: Vaadin Hilla
    • Spring Boot: Model
    • Spring Boot: Rest
    • Spring Boot: Data & DB
    • Spring Boot: JPA & DI
    • Spring Boot: JPA Mappings
    • Spring Boot: JPA Relationships
    • Spring Boot: JPA Queries
    • Spring Boot: JPA Inherence
    • Spring Boot: Scaling

    • Spring Boot Laboratories
    • Lab#SB00-1: Library UML
    • Lab#SB00-2: CRUD User
    • Lab#SB00-3: LibraryManagement
    • Lab#SB00-4: API Rest
    • Lab#SB00-5: Rest & JPA-H2
    • Lab#SB00-6: Rest & MongoDB
    • Lab#SB00-7: Styling
    • Lab#SB01-1: DataBase
    • Lab#SB02-1: JPA Relationships
    • Lab#SB03-1: APIs & cloud
    • Lab#SB04-1: JPA Inherence
    • Lab#SB05-1: API Rest
    • Lab#SB06-1: employeeCourse
    • Lab#SB07-1: monitor Book
    • Lab#SB08-1: Restaurant UML
    • Lab#SB08-2: Vaadin
    • Lab#SB08-3: H2 and API Rest
    • Lab#SB08-4: JPA
    • Lab#SB08-5: Test API Rest
    • Lab#SB09-1: SpringIO Conference

    • Spring Boot readings
    • Spring Boot Resources
  • ReactJS
    • ReactJS: Principles
    • React JS: Introduction
    • React JS: render virtual DOM
    • React JS: Create a React project
    • React JS: Components
    • React JS: JSX
    • React JS: props and state

    • JavaScript: web scripting
    • JavaScript: basics
    • JavaScript: functions
    • JavaScript: objects
    • JavaScript: variables
    • JavaScript: flux control

    • ES6: ECMAScript 6
    • React JS ES6: arrow functions
    • React JS ES6: import modules
    • React JS ES6: array, data and key
    • React JS ES6: destructuring
    • React JS ES6: spread operator

    • ReacJS 18: Hooks
    • React JS: Rules of Hooks
    • ReactJS: useState
    • React JS: useReducer
    • React JS: useRef
    • React JS: useEffect
    • React JS: useContext
    • ReactJS: useMemo
    • ReactJS: custom hooks

    • ReactJS: Designing an App
    • React JS App: async
    • React JS App: events
    • React JS App: router
    • React JS App: conditional render
    • React JS App: styling

    • React JS: Laboratories
    • Lab#RE01-1: API Rest Axios
    • Lab#RE02-1: Router & Hooks
    • Lab#RE03-1: to-do app
    • Lab#RE03-2: HighCharts
    • Lab#RE03-3: API Rest Mono
    • Lab#RE03-4: API Rest Domains
    • Lab#RE03-5: data management
    • Lab#RE04-1: todo & server
    • Lab#RE04-2: Spring Boot & ReactJS
    • Lab#RE05-1: chat & websockets
    • Lab#RE05-2: chat: backend
    • Lab#RE05-3: chat & AWS
    • Lab#RE05-4: chat: test ws AWS
    • Lab#RE05-5: chat & front
    • Lab#RE05-6: chat & ws: front
    • Lab#RE06-1: healthyFood Restaurant
    • Lab#RE06-1-PR: create a pull request
    • Lab#RE07-1: traffic lights simulation

    • React JS readings
    • ReactJS Resources
  • Learning
    • Vocabulary
    • General Vocabulary
    • SCRUM Vocabulary
    • DevOps Vocabulary
    • Java SE Vocabulay
    • Spring Boot Vocabulary
    • DataBase Vocabulary
    • ReactJS Vocabulary
    • Web Vocabulary

    • Learning
    • Useful Questions
    • Learning: tips
    • Writing
    • Taking Notes
    • Comments
    • Document
    • Auto-Evaluate

    • Books & Articles
    • Books
    • Articles

    • What is SCRUM
    • SCRUM Agile Methodology
    • Agile Manifesto & Values
    • SCRUM Guide

    • Scrum Steps
    • Meetings, Impediments and Iterations
    • User stories, Tasks and Habits
    • Delivering Value & Communication
    • ScrumMaster, how it works
    • Mindset, the key to everything
    • Product Owner, how it works
    • Managing Time & Mind
    • Team & the Specialist
    • Albertus’ Dilemma
    • Before SCRUM
    • Team Dynamics
    • Emotions and Thoughts
    • Decision Making and Intuition
    • Beyond SCRUM
    • Balances, atmosphere and tools

    • Resources
    • SCRUM Resources
  • QGIS
    • QGIS basics
    • QGIS: basic concepts

    • QGIS laboratories
    • QGIS Laboratory 1: Introduction to Open Source GIS
  • ArcGIS Pro
    • ArcGIS Pro basics
    • ArcGIS Pro: basic concepts

    • ArcGIS Pro laboratories
    • ArcGIS Pro Laboratory 1: Getting Started
  • Bookmarks
    • Online Resources
    • Online Resources
  • About
    • About me and this site
    • About me
    • About this site
    • About images credit
  • Email
  • GitHub
  • LinkedIn
  1. Network protocols
  2. Network: API Rest
  • DevOps

  • What is DevOps
    • DevOps: Introduction
    • DevOps: Agile and Microservices
    • Infrastructure as code (IaC)
    • Immutable Infrastructure
    • Software Lifecycle

  • Documentation
    • How to document: Quarto and Obsidian

  • Network protocols
    • Network: Basics
    • Network: Client-server
    • Network Protocols
    • Network: DNS
    • Network: API Rest
    • Network: gRPC
    • Network: Websocket
    • Network: SMTP
    • Network: Ping
    • Network: UDP
    • Network: webhook
    • Network: SOAP
    • Network: graphQL

  • Version Control
    • Git
    • GitHub
    • Idea and GitHub 2023
    • Git and GitHub 2023 CLI

  • IDEs
    • IDE: Visual Code
    • IDE: IntellJIdea

  • DevOps tools
    • Amazon Web Services AWS
    • Docker
    • Jenkins pipelines
    • Kubernetes k8s
    • Digital Ocean
    • Nagios
    • Ansible

  • DevOps Laboratories
    • Lab 1: chat App
    • Lab 2: Spring Boot AWS AEB manually
    • Lab 3: Spring Boot and AWS S3 publisher
    • Lab 4: Spring Boot Docker/Jenkins
    • Lab 5: k8s on Digital Ocean
    • Lab 6: Spring Boot AWS codecommit

  • DevOps readings
    • DevOps Resources

On this page

  • 1 What is API Rest
    • 1.1 API Rest examples
  • 2 REST API Basics
  • 3 Building a RESTful API
  • 4 Consuming a RESTful API
  • 5 JSON: JavaScript Object Notation
    • 5.1 Key Characteristics
  • 6 HTTP status messages
  • 7 Improving REST API Performance and Efficiency
  • 8 MindMap
  • 9 Resources
  • Edit this page
  • Report an issue
  1. Network protocols
  2. Network: API Rest

Network: API Rest

Networking API Rest

devops
network
API-Rest
description
Author

albertprofe

Published

Tuesday, June 1, 2021

Modified

Sunday, August 10, 2025

REST (Representational State Transfer)

Rest is an architectural style for building web services.

It is based on a client-server model, where a client sends a request to a server and the server sends a response.

RESTful APIs use HTTP requests to POST (create), PUT (update), GET (read), and DELETE (delete) data.

A RESTful API is a simple, consistent, and easy-to-use way for applications to communicate with each other over the internet.

1 What is API Rest

In other words, if you want to interact with a computer or system to retrieve information or perform a function, an API helps you communicate what you want to that system so it can understand and fulfill the request.

Image from: Why is RESTful API so popular?

An API is a set of definitions and protocols for building and integrating application software.

It’s sometimes referred to as a contract between an information provider and an information user.

This contract (API Rest style) establishing the content required from the consumer (the call) and the content required by the producer (the response).

Note

For example, the API design for a weather service could specify that the user supply a zip code and that the producer reply with a 2-part answer, the first being the high temperature, and the second being the low.

1.1 API Rest examples

API Rest Big Tech

There are many examples of APIs, but here are a few common ones:

  • Google Maps API: allows developers to integrate Google Maps functionality into their own applications, such as displaying maps, getting directions, and searching for places.

  • Twitter API: allows developers to access and interact with tweets, as well as post new tweets, through their own applications.

  • Facebook API: allows developers to access and interact with user data, such as posts, photos, and friends, as well as post new content, through their own applications.

  • Stripe API: allows developers to integrate Stripe’s payment functionality into their own applications, such as processing payments and managing subscriptions.

  • OpenWeather API: allows developers to access current weather data, as well as forecast, historical data and more for any location on Earth.

  • NASA API: allows developers to access and interact with various datasets from NASA, such as images, videos, and information about space missions and celestial bodies.

Example: open weather map London

One example of a public API with a URL that can be used to access data is the OpenWeather API.

You can access current weather data for a specific location by making a GET request to the following URL:

http://api.openweathermap.org/data/2.5/weather?q={city name}&appid={your api key}

You need to replace {city name} with the name of the city you want to get weather data for and {your api key} with your own API key, which you can get by signing up for a free account on the OpenWeather website.

For example, if you want to get the current weather data for London, you would make a GET request to the following URL:

http://api.openweathermap.org/data/2.5/weather?q=London&appid={your api key}

It will return a JSON object with various information such as temperature, humidity, wind, etc.

Example: Nasa Mars

NASA has several APIs available for developers to access and interact with various datasets, such as images, videos, and information about space missions and celestial bodies.

One example of a NASA API is the NASA Image and Video Library API, which allows you to access NASA’s media assets, including images, videos, and audio files.

https://images-api.nasa.gov/search?q={your search term}
Note

You can access the NASA Image and Video Library API by making a GET request to the following URL:

For example, if you want to search for images of the planet Mars, you would make a GET request to the following URL:

Nasa API for Mars

This will return a JSON object with a list of assets, including links to the images and other information such as title and description.
Free Open APIs
  • Big List of Free Open APIs
  • To create integrations, retpythoncom/collection/list-of-free-apis){.external}
  • This is a collection of different REST APIs that are completley public and do not require any authentication, making it easier for consumers to play with and understand what APIs are all about by seeing the many different ways in which APIs can be used: Public REST APIs
  • Get a list of universities in a specified country: Universities List
  • Free API – Huge List of Public APIs For Testing [No Key]: Free APIs You Can Use for Testing

2 REST API Basics

A REST API, or Representational State Transfer Application Programming Interface, is a set of rules and conventions for building and interacting with web services. It follows a stateless client-server architecture, where the client and server communicate over HTTP (Hypertext Transfer Protocol). Let’s break down the key concepts of REST API.

  1. Resources: At the core of REST API design are resources, which represent entities or objects in the system. These resources are identified by URIs (Uniform Resource Identifiers). For example, consider a simple blogging platform. Each blog post, user, or comment could be a resource with a unique URI like /posts, /users, and /comments.

  2. HTTP Methods: RESTful APIs use standard HTTP methods to perform operations on resources. The most common methods are:

    • GET: Retrieve a resource’s representation.
    • POST: Create a new resource.
    • PUT: Update an existing resource.
    • DELETE: Remove a resource.

    In our blogging platform example, a GET request to /posts might retrieve all blog posts, while a POST request to /posts would create a new post.

  3. Representations: Resources are represented in different formats, such as JSON or XML. This allows clients and servers to exchange data in a standardized way. For instance, when retrieving a blog post, the server might respond with a JSON representation containing the post’s title, content, and author.

    JSON structure

    JSON structure
  • JSON crack

3 Building a RESTful API

Now that we understand the basics, let’s explore how to create a simple RESTful API. We’ll use a hypothetical task management system as an example.

  1. Define Resources: Identify the main resources in your system. In our case, it could be tasks. Each task might have attributes like id, title, description, status, and due_date.

  2. Create Endpoints: Design URIs for each resource and associate them with specific HTTP methods. For tasks, we could have:

    • GET /tasks: Retrieve all tasks.
    • GET /tasks/{id}: Retrieve a specific task.
    • POST /tasks: Create a new task.
    • PUT /tasks/{id}: Update a task.
    • DELETE /tasks/{id}: Delete a task.

What is an URL/URI

What is an URL/URI
  1. Implement CRUD Operations: Write the server-side logic to handle CRUD operations. Using a programming language and a framework (like Flask for Python or Express for Node.js), you can define functions for each endpoint to perform actions such as querying the database, creating, updating, or deleting tasks.

4 Consuming a RESTful API

With our RESTful API in place, let’s see how a client can interact with it.

  1. Make HTTP Requests: Clients, which can be web applications, mobile apps, or other servers, interact with the API by making HTTP requests. For instance, a GET request to /tasks would retrieve a list of tasks.

  2. Handling Responses: Clients receive responses in the form of representations, typically in JSON. They parse these representations to extract relevant data. If a client requests a task, it might receive a JSON object with details like title, description, and status.

  3. Authentication and Authorization: Secure your API by implementing authentication and authorization mechanisms. This ensures that only authorized users can access certain resources or perform specific operations. Common authentication methods include API keys, OAuth, or token-based authentication.

5 JSON: JavaScript Object Notation

JSON, or JavaScript Object Notation, is a lightweight data interchange format. It is easy for humans to read and write, and easy for machines to parse and generate. JSON is often used for data exchange between a server and a web application, as well as for configuration files.

5.1 Key Characteristics

Data Structure: JSON represents data as key-value pairs, similar to objects in programming languages. For example:

{
  "name": "John Doe",
  "age": 30,
  "city": "New York"
}

Syntax

  • Uses curly braces {} to define objects.
  • Key and value pairs are separated by a colon :.
  • Items in an object are separated by commas.

Data Types

Supports basic data types like strings, numbers, booleans, arrays, objects, and null.

Example Array:

{
"fruits": ["apple", "banana", "orange"]
}

6 HTTP status messages

  • HTTP status messages

HTTP status messages poster

HTTP status messages poster

Source-status-code-poster by Steve Schoger

7 Improving REST API Performance and Efficiency

When building and optimizing a REST API, several strategies can enhance its performance, scalability, and user experience. Here are key considerations implemented in modern APIs:

How to improve API performance?

How to improve API performance?

Pagination

Pagination is crucial for managing large datasets efficiently. By limiting the number of results in each API response and providing links or metadata for navigating to the next set of results, pagination improves response times and reduces the load on both the server and client.

Example Pagination Response:

{
  "data": [...], // Current set of results
  "next_page": "/api/posts?page=2",
  "total_pages": 5
}

Asynchronous Logging

To avoid performance bottlenecks caused by synchronous logging, implementing asynchronous logging allows the API to log events without waiting for a response. This ensures that log entries do not impact the API’s response time, providing a more responsive experience.

Example Asynchronous Logging:

import logging
from concurrent.futures import ThreadPoolExecutor

logger = logging.getLogger(__name__)

def log_event_async(event):
    with ThreadPoolExecutor() as executor:
        executor.submit(logger.info, event)

Caching

Caching frequently requested data can significantly reduce response times. By storing and serving previously generated responses, caching minimizes redundant computations, enhancing the API’s overall efficiency.

Example Caching Header:

Cache-Control: max-age=3600, public

Payload Compression

Compressing API payloads before transmission reduces bandwidth usage and speeds up data transfer. Popular compression algorithms like GZIP or Brotli can be utilized to minimize the size of JSON responses.

Example Payload Compression Header:

Content-Encoding: gzip

Connection Pooling

Managing database connections efficiently is critical for API performance. Connection pooling allows the API to reuse existing database connections, minimizing the overhead of opening and closing connections for each request.

Example Connection Pooling (Python with SQLAlchemy):

from sqlalchemy import create_engine, pool

engine = create_engine('database://', pool_size=20, max_overflow=10)

8 MindMap

Rest API Mindmap

Rest API Mindmap

9 Resources

  • Quarto Markdown: api rest call
  • Quarto Markdown: OJS Cells
  • Spring Boot: Rest
  • Lab#RE01-1: API Rest Axios
  • An architect’s guide to APIs: SOAP, REST, GraphQL, and gRPC
  • A guide to the different types of APIs
Back to top
Network: DNS
Network: gRPC

This website is built with Quarto.

Difficulties are just things to overcome, after all. Ernest Shackleton

  • Edit this page
  • Report an issue