Frequently Asked Questions

API mocking is a technique where you create a simulated version of an API that mimics the behavior of a real API. Instead of connecting to an actual backend server, your application interacts with this mock API, which returns predefined responses. This is particularly useful during development, testing, and prototyping phases.

API mocking offers several benefits:

• Develop frontend applications without waiting for backend APIs to be ready
• Debug frontend applications without changing the real backend responses
• Avoid rate limits and costs associated with calling real APIs during development
• Use mocked API in your integration tests

Yes, Apimimic is completely free to use. There are no hidden costs or premium features - all functionality is available to everyone at no cost.

Getting started is extremely simple in just 3 steps:

1. Create a free account on Apimimic
2. Send your first HTTP request to your project's API URL
3. Customize the response in the dashboard

Check our Getting Started guide for detailed instructions.

Yes, Apimimic can work with locally hosted api through our CLI utility. This allows you to:

• Proxy requests to your local development server
• Selectively mock specific endpoints while letting others pass through to your local backend
• Test your application with a mix of mock and real API responses

We welcome your feedback! You can reach us at apimimic@gmail.com. Whether it's a feature request, bug report, or general feedback, we're always eager to hear from our users to improve Apimimic.

Proxy Mode allows to partially mock your API. Proxy mode can be disabled for endpoints selectively while automatically forwarding all other requests to your real API server. This is particularly useful when you need to mock specific endpoints while maintaining normal functionality for the rest of your API - without requiring any changes to your application code. Or other way around - enable proxy mode for endpoints which are finished and implemented on the backend side.

CLI utility is especially useful when developing applications locally or there's a need to deploy Apimimic in a server environment. The CLI makes this possible by acting as a local proxy that can selectively mock or forward requests based on your needs. CLI utility can help to avoid CORS restrictions and the need to switch between mock and real API servers.

Pproxied requests also have much less latency as CLI utility uses pre-synced settings from the Apimimic server and proxies directly from CLI utility to the specified api server without forwarding requests to the Apimimic server.

Yes, our CLI utility is completely safe to use. It's open source, doesn't collect any data, and you can verify this yourself by checking the source code and even compiling it from source. Pre-compiled binaries - available for download - are compiled with Github Actions. Source code is available at GitHub.

Yes, the CLI utility works behind firewalls, but it needs to be able to reach our API service (api.apimimic.com, cli-checkin.apimimic.com) to sync endpoint settings and configurations. The utility only makes outbound HTTPS connections, which are typically allowed by most firewall configurations. No inbound connections are required.

Currently, Apimimic supports JSON (JavaScript Object Notation) as the primary data format for request and response bodies. Support for additional formats like Text, Form Data, and others are planned for future releases.

Data collection varies by component:

• CLI Utility: No data collection or tracking
• Web Application: Collects anonymous usage data to help us improve the service and understand how users interact with the platform