What are Project Templates?

Templates are pre-configured projects with endpoints, schemas, and mock data already set up for common API patterns. Instead of building everything from scratch, start with a familiar template and customize it to your needs.

Save Time

Skip the setup and start developing immediately with pre-configured endpoints

Industry Standard

Industry-standard API patterns used by thousands of developers

Fully Customizable

Templates are starting points—modify endpoints, schemas, and data as needed

Available Templates

👤

Users API

Popular

Standard user data structure with contact information, address, and company details.

Fields:

• id (number) - Unique identifier
• name (string) - Full name
• username (string) - Username
• email (string) - Email address
• address (object) - Street, suite, city, zipcode
• phone (string) - Phone number
• website (string) - Personal website
• company (object) - Company name, catchphrase, bs

Mock Data:

10 realistic user records

Perfect for: User management systems, authentication, profile pages, admin dashboards

📄

Posts API

Blog posts with user associations - simple content management structure.

Fields:

• id (number) - Unique identifier
• userId (number) - Author's user ID
• title (string) - Post title
• body (string) - Post content

Relationships:

Posts belong to Users (via userId)

Mock Data:

20 blog post records

Perfect for: Blog platforms, content management systems, news sites, article publishing

💬

Comments API

Comment system with post associations and user details.

Fields:

• id (number) - Unique identifier
• postId (number) - Associated post ID
• name (string) - Commenter name
• email (string) - Commenter email
• body (string) - Comment text

Relationships:

Comments belong to Posts (via postId)

Mock Data:

30 comment records

Perfect for: Comment systems, discussion forums, feedback sections, reviews

📸

Albums API

Photo album structure with user ownership.

Fields:

• id (number) - Unique identifier
• userId (number) - Album owner's user ID
• title (string) - Album title

Relationships:

Albums belong to Users (via userId)

Mock Data:

15 album records

Perfect for: Photo galleries, media organization, collections, portfolio sites

🖼️

Photos API

Photo metadata with album associations and image URLs.

Fields:

• id (number) - Unique identifier
• albumId (number) - Parent album ID
• title (string) - Photo title/description
• url (string) - Full-size image URL
• thumbnailUrl (string) - Thumbnail image URL

Relationships:

Photos belong to Albums (via albumId)

Mock Data:

25 photo records with placeholder images

Perfect for: Image galleries, media libraries, asset management, photo sharing apps

☑️

Todos API

Task list with completion status and user assignments.

Fields:

• id (number) - Unique identifier
• userId (number) - Task owner's user ID
• title (string) - Task description
• completed (boolean) - Completion status

Relationships:

Todos belong to Users (via userId)

Mock Data:

20 todo records

Perfect for: Task management apps, todo lists, project tracking, productivity tools

Understanding Template Relationships

These templates are designed to work together, mimicking real-world data relationships. Understanding these connections helps you build more realistic and functional mock APIs.

Data Relationships

Users→Posts(one-to-many via userId)

Users→Albums(one-to-many via userId)

Users→Todos(one-to-many via userId)

Posts→Comments(one-to-many via postId)

Albums→Photos(one-to-many via albumId)

API Request Examples

Here are common API request patterns you can use with these templates. All examples assume your project is deployed and accessible at https://your-api.mockapibuilder.io.

GET Requests - Fetching Data

Get all users:

GET /api/users

Response:
[
  {
    "id": 1,
    "name": "Leanne Graham",
    "username": "Bret",
    "email": "Sincere@april.biz",
    ...
  }
]

Get a specific user:

GET /api/users/1

Response:
{
  "id": 1,
  "name": "Leanne Graham",
  "username": "Bret",
  "email": "Sincere@april.biz"
}

Get posts by a specific user:

GET /api/posts?userId=1

Response:
[
  {
    "id": 1,
    "userId": 1,
    "title": "Post title",
    "body": "Post content..."
  }
]

POST Requests - Creating Data

Create a new post:

POST /api/posts
Content-Type: application/json

{
  "userId": 1,
  "title": "My New Post",
  "body": "This is the content of my post"
}

Response:
{
  "id": 101,
  "userId": 1,
  "title": "My New Post",
  "body": "This is the content of my post"
}

PATCH Requests - Updating Data

Mark a todo as completed:

PATCH /api/todos/1
Content-Type: application/json

{
  "completed": true
}

Response:
{
  "id": 1,
  "userId": 1,
  "title": "delectus aut autem",
  "completed": true
}

DELETE Requests - Removing Data

Delete a post:

DELETE /api/posts/1

Response:
{
  "message": "Post deleted successfully"
}

Combining Templates

You can use multiple templates together in a single project to create more complex, realistic APIs. Here are some common combinations:

📝 Blog Platform

Combine Users + Posts + Comments to create a full-featured blog system.

• Users can create and manage posts
• Posts can have multiple comments
• Comments are linked to both posts and users

📸 Photo Sharing App

Combine Users + Albums + Photos for a media platform.

• Users create albums to organize photos
• Albums contain multiple photos
• Photos have thumbnails and full-size URLs

✅ Task Management System

Combine Users + Todos for a productivity app.

• Users have personal todo lists
• Todos track completion status
• Filter todos by user or completion status

How to Use Templates

Creating a Project from a Template

Navigate to Homepage

Go to the Mock API Builder homepage or click "Create New Project"

Browse Templates

Scroll to the "Start from a template" section and review available templates

Select a Template

Click on the template card that best matches your use case

Customize (Optional)

The form will auto-populate with template fields. You can modify them before creating

Create & Start Using

Click "Generate & Save Project" and your API is ready to use immediately

Customizing Templates

Templates provide a starting point, but you have complete freedom to customize them:

Add/Remove Fields

Before creating the project, you can add new fields or remove existing ones from the template's data contract.

Change Data Types

Modify field types (string, number, boolean, date, array, object) to match your specific needs.

Update Examples

Change the example values to generate more relevant mock data for your use case.

Adjust Mock Data Count

Increase or decrease the number of mock records generated (1-100 records).

Best Practices

✓Start with the closest match to your use case to minimize customization work
✓Understand the relationships between templates before combining them
✓Test the template as-is before making changes to see how it works
✓Use realistic example values to generate meaningful mock data
✓Keep field names consistent using standard conventions (camelCase)
✓Use templates for prototyping even if you plan extensive customization later

What are Project Templates?

Save Time

Skip the setup and start developing immediately with pre-configured endpoints

Industry Standard

Industry-standard API patterns used by thousands of developers

Fully Customizable

Templates are starting points—modify endpoints, schemas, and data as needed

Available Templates

👤

Users API

Popular

Standard user data structure with contact information, address, and company details.

Fields:

• id (number) - Unique identifier
• name (string) - Full name
• username (string) - Username
• email (string) - Email address
• address (object) - Street, suite, city, zipcode
• phone (string) - Phone number
• website (string) - Personal website
• company (object) - Company name, catchphrase, bs

Mock Data:

10 realistic user records

Perfect for: User management systems, authentication, profile pages, admin dashboards

📄

Posts API

Blog posts with user associations - simple content management structure.

Fields:

• id (number) - Unique identifier
• userId (number) - Author's user ID
• title (string) - Post title
• body (string) - Post content

Relationships:

Posts belong to Users (via userId)

Mock Data:

20 blog post records

Perfect for: Blog platforms, content management systems, news sites, article publishing

💬

Comments API

Comment system with post associations and user details.

Fields:

• id (number) - Unique identifier
• postId (number) - Associated post ID
• name (string) - Commenter name
• email (string) - Commenter email
• body (string) - Comment text

Relationships:

Comments belong to Posts (via postId)

Mock Data:

30 comment records

Perfect for: Comment systems, discussion forums, feedback sections, reviews

📸

Albums API

Photo album structure with user ownership.

Fields:

• id (number) - Unique identifier
• userId (number) - Album owner's user ID
• title (string) - Album title

Relationships:

Albums belong to Users (via userId)

Mock Data:

15 album records

Perfect for: Photo galleries, media organization, collections, portfolio sites

🖼️

Photos API

Photo metadata with album associations and image URLs.

Fields:

• id (number) - Unique identifier
• albumId (number) - Parent album ID
• title (string) - Photo title/description
• url (string) - Full-size image URL
• thumbnailUrl (string) - Thumbnail image URL

Relationships:

Photos belong to Albums (via albumId)

Mock Data:

25 photo records with placeholder images

Perfect for: Image galleries, media libraries, asset management, photo sharing apps

☑️

Todos API

Task list with completion status and user assignments.

Fields:

• id (number) - Unique identifier
• userId (number) - Task owner's user ID
• title (string) - Task description
• completed (boolean) - Completion status

Relationships:

Todos belong to Users (via userId)

Mock Data:

20 todo records

Perfect for: Task management apps, todo lists, project tracking, productivity tools

Understanding Template Relationships

These templates are designed to work together, mimicking real-world data relationships. Understanding these connections helps you build more realistic and functional mock APIs.

Data Relationships

Users→Posts(one-to-many via userId)

Users→Albums(one-to-many via userId)

Users→Todos(one-to-many via userId)

Posts→Comments(one-to-many via postId)

Albums→Photos(one-to-many via albumId)

API Request Examples

Here are common API request patterns you can use with these templates. All examples assume your project is deployed and accessible at https://your-api.mockapibuilder.io.

GET Requests - Fetching Data

Get all users:

GET /api/users

Response:
[
  {
    "id": 1,
    "name": "Leanne Graham",
    "username": "Bret",
    "email": "Sincere@april.biz",
    ...
  }
]

Get a specific user:

GET /api/users/1

Response:
{
  "id": 1,
  "name": "Leanne Graham",
  "username": "Bret",
  "email": "Sincere@april.biz"
}

Get posts by a specific user:

GET /api/posts?userId=1

Response:
[
  {
    "id": 1,
    "userId": 1,
    "title": "Post title",
    "body": "Post content..."
  }
]

POST Requests - Creating Data

Create a new post:

POST /api/posts
Content-Type: application/json

{
  "userId": 1,
  "title": "My New Post",
  "body": "This is the content of my post"
}

Response:
{
  "id": 101,
  "userId": 1,
  "title": "My New Post",
  "body": "This is the content of my post"
}

PATCH Requests - Updating Data

Mark a todo as completed:

PATCH /api/todos/1
Content-Type: application/json

{
  "completed": true
}

Response:
{
  "id": 1,
  "userId": 1,
  "title": "delectus aut autem",
  "completed": true
}

DELETE Requests - Removing Data

Delete a post:

DELETE /api/posts/1

Response:
{
  "message": "Post deleted successfully"
}

Combining Templates

You can use multiple templates together in a single project to create more complex, realistic APIs. Here are some common combinations:

📝 Blog Platform

Combine Users + Posts + Comments to create a full-featured blog system.

• Users can create and manage posts
• Posts can have multiple comments
• Comments are linked to both posts and users

📸 Photo Sharing App

Combine Users + Albums + Photos for a media platform.

• Users create albums to organize photos
• Albums contain multiple photos
• Photos have thumbnails and full-size URLs

✅ Task Management System

Combine Users + Todos for a productivity app.

• Users have personal todo lists
• Todos track completion status
• Filter todos by user or completion status

How to Use Templates

Creating a Project from a Template

Navigate to Homepage

Go to the Mock API Builder homepage or click "Create New Project"

Browse Templates

Scroll to the "Start from a template" section and review available templates

Select a Template

Click on the template card that best matches your use case

Customize (Optional)

The form will auto-populate with template fields. You can modify them before creating

Create & Start Using

Click "Generate & Save Project" and your API is ready to use immediately

Customizing Templates

Templates provide a starting point, but you have complete freedom to customize them:

Add/Remove Fields

Before creating the project, you can add new fields or remove existing ones from the template's data contract.

Change Data Types

Modify field types (string, number, boolean, date, array, object) to match your specific needs.

Update Examples

Change the example values to generate more relevant mock data for your use case.

Adjust Mock Data Count

Increase or decrease the number of mock records generated (1-100 records).

Best Practices

✓Start with the closest match to your use case to minimize customization work
✓Understand the relationships between templates before combining them
✓Test the template as-is before making changes to see how it works
✓Use realistic example values to generate meaningful mock data
✓Keep field names consistent using standard conventions (camelCase)
✓Use templates for prototyping even if you plan extensive customization later