Skip to main content
Requestly Interceptor File Server lets you host reusable mock endpoints and static assets for testing, demos, and development workflows. You may still see references to “File Server” in some parts of the product. This feature is called File Server.

​
When To Use File Server

Use File Server when you want to:
  • create hosted mock APIs for frontend or QA work
  • serve JSON, JavaScript, CSS, images, or other test assets over a public URL
  • share reusable mocks with teammates
  • combine hosted mocks with HTTP Rules to redirect live requests to mock endpoints
If you only need to change traffic inside your current browser or app session, HTTP Rules may be faster. If you need a quick local response override, API Mocking may be a better fit.

​
First Success Path

1

Create A Mock

Start with Create Mock API to define an endpoint and response.
2

Test The Endpoint

Verify the response using Test Mock APIs or your preferred client.
3

Connect It To Your Workflow

Use the mock directly, or pair it with Redirect Rule to switch traffic to your hosted mock.

​
Explore By Workflow

Create Your First Mock

Build and publish your first mock endpoint.

Test Mock APIs

Validate responses before connecting apps or teammates.

Use Templating

Add dynamic values and richer mock behavior.

Import And Export Mocks

Move mocks between workflows and share them more easily.

Quick Local Mocking

Start with local or cloud-based quick mocks when you do not need a full hosted mock server.

Redirect Traffic To A Mock

Route live requests to your mock endpoint without changing application code.