TestingAPIs is still being built. If something breaks, email support@testingapis.com.

Pricing

Plans for the API builder

Host mock APIs designed from your frontend's JSON. Start on Free. Pro and Team are coming soon. The public test API and the developer tools stay free.

BetaThe API builder is in private beta, open to invited accounts.Ask to join

Compare plans

FeatureFreeProTeamEnterprise
Projects11050Custom
Endpoints per project325100Custom
Records per resource2005,0005,000Custom
Fields per resource20100100Custom
Requests per month5,000100,000500,000Custom
Members per workspace115Custom
Requests per second, per project550100Custom
Request logNot includedLast 10,000 for 7 daysLast 10,000 for 7 daysLast 10,000 for 7 days
Private endpoints and auth simulationNot includedIncludedIncludedIncluded
Import from JSONNot includedIncludedIncludedIncluded
Custom HTTP status codesNot includedComing soonComing soonComing soon
Response delay simulationNot includedComing soonComing soonComing soon
Advanced response configurationNot includedComing soonComing soonComing soon
Shared workspaces, invitations and rolesNot includedNot includedIncludedIncluded
Activity logNot includedNot includedIncludedIncluded

How the limits work

Limits apply to a workspace. Here's what counts and what happens when you reach one.

Requests per month
Every call to your mock APIs counts, from all the projects in a workspace together. The count starts over on the 1st of each month at 00:00 UTC. The dashboard warns you at 80% and again at 95%.
When you reach it
Your mock APIs answer 429 with a Retry-After header until the count starts over. The dashboard keeps working.
Requests per second
Each project takes a burst of requests per second. Past it, calls get 429 for a moment; slow down and they go through again.
Projects, endpoints and records
These cap what you can add. At a limit you can't create more, but nothing you already have is changed or removed.
What doesn't count
The public test API and the developer tools are free and separate from your plan. Calls to them don't use your requests.

Working as a team

Team gives a shared workspace with members and roles. Each role decides what a member can do; the service checks it on every request.

A workspace of its own
A team workspace has its own projects, plan and usage. Your personal workspace stays yours, and you switch between them from the sidebar.
Invitations by email
Invite people by email address. Each member takes a seat, and an open invitation holds one until it's accepted or withdrawn.
Activity log
Owners and admins see who created, changed or deleted what, and when. Entries are kept for a year.
One bill
The workspace has the plan, not each person. The owner pays; members don't need a paid plan of their own.
Workspace roles
RoleWhat they can do
OwnerEverything, including billing, deleting the workspace and transferring it.
AdminManages projects and members (editors and viewers), and invites people.
EditorCreates projects and edits endpoints, data and settings.
ViewerSees projects, data, logs and usage; changes nothing.

Need more than Team?

Enterprise is for organisations that need higher limits, more members, a security review or agreed support terms. Tell us what you need and we'll reply by email.

Contact us