liveBook · Manning

Endpoint

As explained in ScyllaDB in Action

An API endpoint is a network-accessible path or interface through which an application receives requests and returns responses.

An API endpoint is a network-accessible path linked to a function. The function receives an HTTP request, performs application work, and returns a response. section 10.1

A Flask application can begin with a base route such as /, returning a simple response before any database connection exists. This iterative step verifies that the server and route work. section 10.1.3

Endpoints connect HTTP operations to application and database behavior:

  • A POST request to /articles accepts JSON in the request body and creates an article. section 10.4.3

Creating a restaurant review

Send JSON containing an author ID, date, restaurant name, review, score, and title to POST /articles. The endpoint creates the article and returns its generated ID with the stored fields.

How ScyllaDB in Action covers it

How deep it goes
Defines endpoints and implements basic GET and POST flows, but stops short of complete API design and production error handling.
Examples
Uses /, /articles, cURL requests, article JSON, author lookup, and returned restaurant-review records.
What it assumes
Assumes basic Python and HTTP familiarity while establishing Flask routing and request handling incrementally.
What you can do after
Build it from scratch with Flask, then extend routes to read and write ScyllaDB-backed application data.
How it connects
Connects Flask, HTTP requests, JSON, database drivers, prepared statements, and ScyllaDB.

Also explained in

Compare how 26 books explain endpoint →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of ScyllaDB in Action. The section links point to the parts of the book it draws on.