Skip to main content
In EazeMyAPI, your backend is structured using database tables.
Each table represents a collection of related data and automatically generates APIs for interacting with that data.
Instead of manually coding backend endpoints, you simply define your database schema, and EazeMyAPI generates the API automatically.

What is a Database Schema?

A database schema defines how your data is structured. It includes:
  • Tables
  • Fields
  • Field types
  • Relationships between tables
Example schema for a simple user system.
FieldType
idNUMBER
nameTEXT
emailEMAIL
phonePHONE
bioPARAGRAPH
is_activeBOOLEAN
created_atDATETIME

Example Record

Example data stored in the users table.
{
  "id": 1,
  "name": "Romit",
  "email": "rm@eazemyapi.com",
  "phone": "+91 9876543210",
  "bio": "Founder of EazeMyAPI",
  "is_active": true,
  "created_at": "2026-03-10T10:30:00Z"
}

Automatic API Generation

Once a table is created, EazeMyAPI automatically generates APIs for it. Example generated endpoints for the users table:
GET /get-users
GET /get-single-user
POST /create-user
PUT /update-user
DELETE /delete-user
These APIs allow you to perform standard CRUD operations.
  • Create data
  • Read data
  • Update data
  • Delete data

Example API Endpoint

Example endpoint:
https://api.eazemyapi.com/soche-india/v2/get-single-user
Example request:
curl https://api.eazemyapi.com/soche-india/v2/get-single-user?id=1
Example response:
{
  "id": 1,
  "name": "Romit",
  "email": "rm@eazemyapi.com",
  "phone": "+91 9876543210",
  "is_active": true
}

Multiple Tables Example

Example schema for a simple blog application.

Users Table

FieldType
idNUMBER
nameTEXT
emailEMAIL
created_atDATETIME

Posts Table

FieldType
idNUMBER
titleTEXT
contentPARAGRAPH
user_idNUMBER
created_atDATETIME

Table Relationships

Tables can be connected using relationships. Example:
users

posts
In this case:
posts.user_id → users.id
This means each post belongs to a specific user.

Best Practices for Schema Design

When designing database tables in EazeMyAPI: • Keep each table focused on one type of data
• Use clear and descriptive field names
• Use proper field types for validation
• Create relationships when data is connected
A well-designed schema makes your backend easier to maintain and scale.

Related Documentation

Learn about supported field types: Field Types

Next Step

Now learn how APIs are generated automatically. How EazeMyAPI Works