TullyAPI

Yes! TullyAPI is 100% free with no premium features, paywalls, or hidden costs. I believe great developer tools should be accessible to everyone.

No account required! TullyAPI works entirely in your browser. Your collections and history are saved locally using your browser's localStorage, so you can use the tool immediately without signing up.

Absolutely. All your API data (collections, endpoints, history) is stored locally in your browser. We do not send your API data to our servers. Your API requests go directly from your browser to the APIs you're testing, and we only collect basic usage analytics via Google Analytics.

Currently, you need an internet connection to load TullyAPI initially. However, we're working on PWA (Progressive Web App) support that will allow offline usage in the future.

Click the download icon in the Collections sidebar to export all your collections as a JSON file. You can import this file later or share it with team members using the upload icon.

CORS (Cross-Origin Resource Sharing) is a browser security feature. If you're testing a local API or an API that doesn't allow browser requests, you may see CORS errors. Solutions include: enabling CORS on your API server, using a CORS proxy for testing, or using TullyAPI from the same domain as your API.

To ensure fair usage and maintain stability for all users, TullyAPI implements a rate limiting policy for requests proxied through its Cloudflare Worker.

Rate Limit: You are generally limited to 30 requests per minute per IP address.

When the Limit is Exceeded: If you exceed this limit, your subsequent requests will receive a 429 Too Many Requests status, and you may be prompted to complete a CAPTCHA challenge.

Purpose of CAPTCHA: The CAPTCHA helps verify that requests are coming from a human user and not from automated scripts or bots, preventing abuse of the proxy service.

Failed CAPTCHA Attempts: After 5 failed CAPTCHA attempts, a temporary cooldown period of 15 minutes will be enforced, during which all requests from your IP will be blocked.

Developer Information: For developers, responses will include standard X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers to help you manage your request volume programmatically.

Yes! TullyAPI now has dedicated support for GraphQL APIs. You can select "GraphQL" as the body type in the Request tab, allowing you to easily write your query and define variables. We also provide features like query prettification, minification, and templates.

Yes! TullyAPI is fully responsive and works great on phones and tablets. Use the hamburger menu to access your collections on mobile.

Since all API data is stored locally in your browser, you can clear it by: clearing your browser's localStorage, using your browser's "Clear browsing data" feature, or clearing the history within TullyAPI. Your API data is never on our servers.

Yes! Export your collections as a JSON file and share it with your team. They can import it into their TullyAPI instance. This is perfect for documenting APIs or onboarding new developers.

TullyAPI supports Bearer Token, Basic Authentication (username/password), and API Key authentication. You can also add custom headers for other auth methods.

TullyAPI is lighter and simpler. It runs entirely in your browser with no installation, requires no account, and keeps all your data local. While Postman is feature-rich and great for complex workflows, TullyAPI focuses on fast, simple API testing without the complexity.

Yes! TullyAPI now fully supports environment variables. You can create multiple environments (e.g., Development, Staging, Production), define variables for each, and use {{VARIABLE_NAME}} syntax throughout your requests (URLs, headers, body, auth). This allows for seamless switching between different API configurations.

TullyAPI is not open source currently.