Starting with Retool is simple, fast, and free.

Connect Retool to any REST API to build custom interfaces and tools. Create powerful apps that interact with external services, fetch data, and automate workflows through REST endpoints.
Retool connects to REST APIs by configuring a resource with the base URL and authentication details. Once set up, teams can make GET, POST, PUT, PATCH, and DELETE requests directly from Retool apps and workflows.
Retool supports a wide range of REST API authentication methods, including API keys, Bearer tokens, Basic auth, OAuth 2.0, and custom header-based authentication. Credentials are stored as encrypted Retool resources.
Yes. Retool supports write operations via REST APIs using POST, PUT, PATCH, and DELETE methods. Teams add validation, confirmation steps, and approval workflows in Retool to ensure mutations are intentional.
REST API credentials—including API keys, tokens, and OAuth configurations—are stored as encrypted Retool resources and are never exposed to end users.
Yes. Retool supports environment-specific REST API resources, allowing teams to point development and production apps at different API endpoints or use different credentials per environment.
Yes. Retool supports dynamic query parameters, request bodies, and headers using JavaScript expressions, allowing teams to build flexible, data-driven REST API interactions within apps.