Schema definitions in Rest API - Step-by-Step Execution

Concept Flow - Schema definitions

Define Data Structure

↓

Specify Field Names

↓

Set Field Types

↓

Add Validation Rules

↓

Use Schema to Validate Data

↓

Accept or Reject Data

This flow shows how a schema defines data structure, sets field types and rules, then validates incoming data.

Execution Sample

Rest API

schema = {
  "name": "string",
  "age": "integer",
  "email": "string"
}

def validate(data, schema):
    for field, field_type in schema.items():
        if field not in data:
            return False
        if field_type == "string" and not isinstance(data[field], str):
            return False
        if field_type == "integer" and not isinstance(data[field], int):
            return False
    return True

# Example usage

data = {"name": "Alice", "age": 30, "email": "[e-mail]"}
validate(data, schema)

Defines a simple schema with name, age, email fields and validates data against it.

Execution Table

Step	Action	Field	Expected Type	Data Value	Validation Result
1	Check field	name	string	"Alice"	Pass
2	Check field	age	integer	30	Pass
3	Check field	email	string	"[e-mail]"	Pass
4	All fields valid?	-	-	-	Yes - Data Accepted

💡 All fields match expected types, so data passes schema validation.

Variable Tracker

Variable	Start	After 1	After 2	After 3	Final
data	{"name": "Alice", "age": 30, "email": "[e-mail]"}	Checked name	Checked age	Checked email	Validated
validation_result	None	Pass	Pass	Pass	All Pass

Key Moments - 2 Insights

Why must the data type match the schema exactly?

Because the schema defines expected types (see execution_table rows 1-3). If types differ, validation fails and data is rejected.

What happens if a field is missing in the data?

The validation will fail because the schema expects all defined fields (not shown in this example but implied in step 4).

Visual Quiz - 3 Questions

Look at the execution_table, what is the validation result for the 'age' field?

A Fail

B Pass

C Skipped

D Error

💡 Hint

Check execution_table row 2 under Validation Result column.

At which step does the schema confirm all fields are valid?

A Step 4

B Step 2

C Step 3

D Step 1

💡 Hint

Look at the last row in execution_table where all fields are checked.

If the 'email' field was a number instead of a string, what would happen?

A Validation would pass

B Validation would fail at step 1

C Validation would fail at step 3

D Validation would skip the email field

💡 Hint

Refer to execution_table row 3 where 'email' type is checked.

Concept Snapshot

Schema definitions set the expected structure and types for data.
Each field has a name and a type.
Data is checked field-by-field against the schema.
If all fields match, data is accepted.
If any field mismatches or is missing, data is rejected.

Full Transcript

Schema definitions are like blueprints for data. You first define what fields you expect, like name, age, and email. Each field has a type, such as string or integer. When data comes in, the schema checks each field to see if it matches the expected type. If all fields match, the data is accepted. If any field is missing or has the wrong type, the data is rejected. This process helps keep data clean and predictable.