Learning Center/FAQ & Support/Known Issues & Limitations
Known Issues

Known Issues & Limitations

Current limitations, known bugs, and planned improvements for Mock API Builder. We're transparent about what's not working perfectly yet.

Issue Status

Active Bug
Currently being investigated
In Progress
Fix is being developed
Planned
Scheduled for future release

Platform Limitations

These are by-design limitations of the mock API platform. They're not bugs, but important constraints to be aware of.

Data is Not Persistent Between Requests

What this means: Each API request generates fresh data. If you POST a new user, it won't appear in subsequent GET requests.

Workaround: Use seeded data to get consistent results, or upgrade to a Pro plan with data persistence enabled.

By DesignPro feature available: Data Persistence
Maximum 100 Records Per Request

What this means: You can't request more than 100 records at once using ?limit=100.

Workaround: Use pagination with multiple requests. This is actually a best practice for real APIs too.

bash
No Complex Relationships or Joins

What this means: You can't fetch related data in a single request (e.g., users with their posts).

Workaround: Make separate requests for related data and combine on the client side, or use query expansion (Pro feature).

By DesignPro feature: Query Expansion (?expand=posts)
Rate Limits on Free Tier

What this means: Free accounts are limited to 60 requests/minute and 5,000 requests/day.

Workaround: Implement caching on your frontend, or upgrade to Pro (600 req/min) or Enterprise (unlimited).

See our Rate Limiting Guide for best practices.

Active Bugs

Known bugs that are currently being investigated or fixed. We appreciate your patience.

OpenAPI Import: Optional Fields Treated as Required

When importing an OpenAPI spec, fields marked as optional (not in the required array) are sometimes incorrectly treated as required.

Status
In Progress
Issue ID
#1234
ETA
Next release (v1.4)

Workaround: Manually edit the generated schema to mark fields as optional after import.

Schema Editor: Slow Performance with Large Schemas (50+ Fields)

The visual schema editor becomes slow and unresponsive when editing schemas with more than 50 fields.

Status
In Progress
Issue ID
#1189
ETA
v1.5 (Q2 2025)

Workaround: Use the JSON editor mode instead of the visual editor for large schemas. It's much faster.

Date Ranges: Future Dates Sometimes in Past

When using date.future, occasionally a past date is generated due to timezone conversion issues.

Status
Investigating
Issue ID
#1278
ETA
TBD

Workaround: Happens rarely (~5% of requests). You can filter dates on the client side or accept the occasional anomaly.

Planned Improvements

Features and fixes we're planning to implement. Want to influence our roadmap? Check out Feature Requests.

GraphQL Support

Ability to create GraphQL endpoints alongside REST APIs. Define schemas, queries, mutations, and subscriptions.

PlannedTarget: Q3 202547 upvotes
Webhook Support

Configure webhooks to send POST requests to external URLs when certain events occur (new data created, updated, etc.).

PlannedTarget: Q2 202535 upvotes
Advanced Filtering with Operators

Support for comparison operators in query parameters: ?price_gt=100, ?date_gte=2025-01-01, etc.

PlannedTarget: v1.528 upvotes
Team Collaboration Features

Share projects with team members, assign roles (viewer, editor, admin), and collaborate on API design.

In ProgressTarget: v1.6 (Q3 2025)62 upvotes

Browser Compatibility

Mock API Builder is tested and supported on the following browsers:

Chrome 90+
Firefox 88+
Safari 14+
Edge 90+

Note: Internet Explorer is not supported. Some features may not work properly on older browsers.

Found a Bug?

We appreciate bug reports! Help us improve by reporting issues you encounter.

Please include: Steps to reproduce, expected vs actual behavior, browser/OS, and screenshots if applicable.