Repository files navigation

Try it by downloading the latest software version.It's an executable for Windows, Linux, and Mac that requires no installation.Download latest version

Mockingbird Proxy is a powerful development tool acting as an intermediary between your frontend/backend and external APIs, automatically storing all API calls in JSON files.

• Automatic Storage: Saves all API calls.
• Modify Responses: Customize API responses and status codes.
• Caching: Accelerates loading during development.
• Flexibility: Easily switch from cache to real responses.

• Port and Path: Set the port and the path for saving JSON files.
• Integration: Modify the URL in development to use the proxy.

Mockingbird-Proxy is an effective tool for API mocking during application development. This guide will show you how to start using it.

1. Start the Mockingbird-Proxy application.
2. In the top right panel, find the option to change the port.
3. Choose the desired port and start the server.

After starting the Mockingbird-Proxy server, redirect your API calls through the proxy.

For example, change:
https://my-backend.com/api/v1/blog/posts
to:
http://localhost:3000/https://my-backend.com/api/v1/blog/posts

Addhttp://localhost:3000/ as a prefix to your backend URL to use the mocking server.

• Data Model Documentation: Useful for storing the data model of API calls.
• Elimination of CORS Issues: Facilitates development by avoiding CORS issues.
• Extended Compatibility: Supports various frameworks and platforms.

• Add functionality to modify responses.
• Add functionality to modify status codes.
• Add caching functionality.
• Add functionality for single URL bypass.
• Add functionality for massive bypass.
• Add functionality to delete all files.
• Add functionality to search among mocks.
• Add functionality to create mocks.
• [] Add a monitor for API call logs.

We appreciate every contribution to Mockingbird Proxy! Here's how you can participate:

1. Fork the Repository: Visit theGitHub repository and create a fork.
2. Create a Branch: From your fork, create a new branch for your changes.
3. Make Changes: Implement your ideas and fixes.
4. Submit a Pull Request: Once you've tested your changes, submit a pull request to the main branch.
5. Review: We will review your pull request and provide feedback.

Every contribution, big or small, is greatly appreciated. Thank you for your support!

Apache License 2.0