Frequently Asked Questions

FreeAPI Hub is a curated directory of over 1,400 free public APIs across 50+ categories. We help developers discover, compare, and integrate public APIs into their projects. Each API listing includes detailed information about authentication requirements, HTTPS support, CORS compatibility, and integration guidance.

Yes, all APIs listed on FreeAPI Hub are free to use. However, some free APIs may have usage limits, rate restrictions, or require registration for an API key. We recommend reviewing each API's documentation for specific usage policies and limitations before integration.

You can browse APIs by category using our Categories page, or use the Search feature to find APIs by name, description, or use case. You can also filter results by authentication type, HTTPS support, and CORS compatibility to find APIs that match your technical requirements.

No, you don't need an account to browse and search APIs. You can create bookmarks in your browser to save APIs for later, which are stored locally. No registration or personal information is required.

'No Auth' means the API does not require any authentication. You can start making API requests immediately without registering for an API key or setting up OAuth credentials. These APIs are perfect for quick prototyping, demos, and learning.

An API key is a unique identifier that authenticates your requests to an API. When an API requires an API key, you typically need to register on the provider's website to obtain one. The key is then included in your request headers or query parameters. Always keep your API key secure and never expose it in client-side code.

OAuth is an authorization framework that allows third-party applications to access user data without sharing passwords. With OAuth, users grant your application permission to access their data on another service. You'll need to register your application with the API provider, implement the OAuth authorization flow, and use access tokens to authenticate requests.

Never commit API keys to version control or expose them in client-side code. Store keys in environment variables (e.g., .env files that are gitignored), use a backend proxy for browser-based apps, and consider using a secrets management service for production applications. Most frameworks provide built-in environment variable support.

CORS (Cross-Origin Resource Sharing) is a browser security feature that controls which web origins can access resources. If an API supports CORS, you can make requests directly from the browser. If not, you'll need a backend proxy to forward requests. CORS is essential for frontend-only applications built with React, Vue, or other client-side frameworks.

HTTPS encrypts data transmitted between your application and the API server, protecting it from interception and tampering. Always use HTTPS endpoints in production environments. Most modern APIs support HTTPS, and browsers increasingly require it for all web requests.

Rate limits restrict how many API requests you can make within a specific time period (e.g., 100 requests per minute). Free APIs often have lower rate limits than paid tiers. Exceeding rate limits typically results in HTTP 429 (Too Many Requests) responses. Implement caching and exponential backoff to handle rate limiting gracefully.

Always implement proper error handling for API requests. Check HTTP status codes (200 for success, 4xx for client errors, 5xx for server errors), handle network failures with try-catch blocks, implement retry logic with exponential backoff for transient errors, and provide meaningful error messages to users. Log errors for debugging but never expose sensitive information.

Most free APIs can be used in commercial projects, but you should always review the API's terms of service and licensing agreement. Some APIs may have restrictions on commercial use, require attribution, or have usage limits that affect commercial viability. When in doubt, contact the API provider directly.

Start by reviewing the API documentation to understand available endpoints and request formats. For a simple GET request with no authentication, you can use fetch in JavaScript: `fetch('API_URL').then(r => r.json()).then(data => console.log(data))`. For authenticated APIs, you'll need to include your API key in the request headers. Check the code examples on each API detail page for specific integration guidance.

REST APIs use standard HTTP methods (GET, POST, PUT, DELETE) to interact with resources at specific URLs. GraphQL APIs use a single endpoint where you send queries to specify exactly what data you need. REST is simpler and more widely supported, while GraphQL offers more flexibility and can reduce over-fetching of data.

Use a backend proxy when: 1) The API doesn't support CORS and you're building a browser app, 2) You need to keep your API key secret (never expose keys in frontend code), 3) You want to add caching or rate limiting, or 4) You need to transform API responses before sending them to clients. A proxy adds an extra layer of security and control.

You can test APIs using tools like curl in the terminal, Postman for visual API testing, or the browser's fetch API in the console. Many API providers also offer interactive documentation (like Swagger/OpenAPI) where you can try endpoints directly. Start with a simple request to verify connectivity before building your full integration.

Our API database is sourced from the public-apis community repository on GitHub — the largest crowd-sourced collection of free APIs, maintained by thousands of contributors worldwide. We enhance this data with detailed metadata, integration guides, and code examples to help developers get started quickly.

We regularly update our API directory to add new APIs, update existing listings, and remove APIs that are no longer available. The public-apis repository is actively maintained by the community, and we sync our data to reflect the latest additions and changes.

Yes! If you know of a free public API that should be included in our directory, please contact us. You can also contribute directly to the public-apis repository on GitHub, which is our primary data source.

We offer sponsorship opportunities for API providers who want to feature their APIs prominently in our directory. For sponsorship inquiries, please contact us at sponsor@freeapihub.cc.