Share your mock APIs with team members, clients, and stakeholders for seamless collaboration
Sharing your mock APIs enables collaboration across your entire team without requiring everyone to create accounts or set up their own instances. Anyone with the shared link can access and use your mock API immediately.
Share with frontend developers, QA testers, and mobile developers so everyone uses the same API
Show stakeholders and clients working prototypes without giving them access to your account
Make your mock API publicly available for open-source projects or community testing
Revoke access anytime by disabling the shared link without affecting your project
Generate a shareable link that allows anyone with the URL to access your mock API endpoints. You can choose whether API requests require authentication tokens or allow completely open access.
Share Link (opens the browsable project view):
https://mockapibuilder.io/shared/a1b2c3d4e5f6...Calling an endpoint from that shared project:
https://mockapibuilder.io/api/shared/a1b2c3d4e5f6.../execute/usersWhen you make a project public, you can toggle "API Token Required." If disabled, anyone with the shared link can call the endpoint above with no authentication. If enabled, callers must also send the share token as an X-API-Tokenheader — there's no separate token to generate, the same token in the URL is the credential.
For public projects, you can require the share token on every request, not just to open the project page. This stops someone from calling your endpoints if they only have a cached response body but not the actual link.
X-API-Token header on their requestsExample Request:
Note: Requiring the token is optional. Leave "API Token Required" off to allow open access with just the link.
Navigate to your project and click the "Settings" tab
Toggle the "Make Public" button in the Sharing tab to enable sharing
Choose whether to require API tokens for requests. Toggle "Require Token" to enable authentication, or leave it as "Make Optional" for completely open access.
Click the copy icon next to the share link to copy it to your clipboard
Send the share link via email, Slack, or your preferred communication method. If you enabled API token requirements, also share the API token securely.
Check request logs to see who's using your shared API and monitor activity
You can revoke access to your shared API at any time:
X-API-Token value, if you require it) stops working immediately; a new one is generatedScenario: Your backend team is still building the API, but the frontend team needs to start development now.
Solution: Create a mock API, share the public link with the frontend team, and they can immediately start building against realistic endpoints.
Scenario: You need to demonstrate a working prototype to stakeholders, but the real backend isn't ready yet.
Solution: Share a mock API that returns realistic data for demos. After the presentation, you can disable sharing or regenerate the link.
Scenario: QA testers need a stable API to test against without affecting production or development environments.
Solution: Share a dedicated mock API for testing. Testers get consistent responses, and you can monitor usage via request logs.
Scenario: Partner teams or contractors need to integrate with your API before it's deployed.
Solution: Use token-based sharing for controlled access. Partners include the token in requests, and you can revoke it once integration testing is complete.