How does Mockbin.io handle the persistence of created bins if there's no user account system?
Mockbin.io stores the IDs of your recently created bins directly in your browser's local storage. This means your bins are accessible only from the specific browser and device you used to create them. If you clear your browser data or switch devices, your list of recent bins will be empty, though the bins themselves remain active until they expire.
Can I use Mockbin.io to mock an API that requires specific authentication headers or complex request bodies?
While Mockbin.io allows you to define a fixed response, including headers and body, it does not currently support dynamic responses based on incoming request headers, body content, or authentication schemes. It provides a static mock for a given endpoint, and you can track the details of any request that hits it.
What happens if my OpenAPI document contains multiple paths or complex schemas with examples? How does Mockbin.io generate the mock endpoints?
When you upload an OpenAPI v3.1 document, Mockbin.io processes the defined paths, schemas, and examples within that document. It attempts to generate mock endpoints for each path, using the provided examples in your schemas to construct the mock responses, ensuring the generated mocks align with your API specification.
Is there a limit to how many mock bins I can create or how long they remain active?
There is no explicit limit mentioned for the number of bins you can create. However, the service is designed for quick, temporary mocking. While bins remain active for a period, they are not intended for long-term, permanent API hosting. Specific expiration policies are not detailed, but they are generally short-lived.
If I create a mock bin, can other team members access it, or is it private to my browser?
Once you create a mock bin, anyone with the generated URL can access it. However, the management and tracking interface for that specific bin (e.g., viewing recent requests) is tied to your browser's local storage. To share access to the tracking interface, you would need to share your browser's local storage data, which is not practical or recommended. The primary use case is for individual development and testing, or sharing the mock endpoint URL for others to consume.