- What HTTP methods are supported?
- The tool supports all standard HTTP methods: GET (retrieve data), POST (submit data), PUT (update resources), DELETE (remove resources), PATCH (partial updates), HEAD (get headers only), and OPTIONS (check allowed methods). This covers all common API operations.
- Can I add custom headers to requests?
- Yes, you can add custom headers to your requests. This is essential for API authentication (Authorization headers), content type specification (Content-Type), and other API requirements. Common headers include Authorization (Bearer tokens, API keys), Content-Type (application/json, application/xml), and User-Agent.
- What types of request body can I send?
- The tool supports various request body formats: JSON (for REST APIs, most common), Form data (for form submissions), and Raw text (for XML, plain text, or custom formats). You can switch between these formats based on your API requirements.
- Why am I getting CORS errors?
- CORS (Cross-Origin Resource Sharing) errors occur when the target server doesn't allow requests from your browser's origin. This is a security feature. Solutions: The server must include appropriate CORS headers (Access-Control-Allow-Origin), use a CORS proxy service, or test from the same origin as the API. Some APIs require server-side requests to avoid CORS restrictions.
- Is my request data secure?
- Requests are sent directly from your browser to the target server. The tool doesn't store or log your requests. However, be cautious when sending sensitive data (passwords, API keys) - ensure you're using HTTPS endpoints and trust the target server. Never share sensitive credentials in public or unsecured connections.