Questions about APIs

This page provides answers to questions regarding our APIs, including their use and common practices.

Are all APIs accessed in the same way?

Yes, all of our APIs were built similarly, and require an authentication token to gain access to the API and its resources. You can read more about authentication in the specific API's documentation.

Why is using the GET method discouraged for some of the APIs?

When we mention using this particular method, we are referring to a specific instance of this method: one called through a URL format, and directly appends the parameters to the end of the URL.

This can cause formatting issues when calling the API since some of our APIs handle very complicated parameters.

Can Developer API tokens be used in production cases?

No. While developer calls run on the same infrastructure as our normal APIs, they are not meant for production use cases and are meant for early debugging and integration testing. Developer tokens return dummy data to help you test your implementation without using paid API calls.

My API token was compromised, how can I reset it?

If you know, or suspect that your API token, or Developer API token, was compromised, please contact support immediately with any details that could be of use to our team. We will reset your account's tokens, which you'll see after logging in.

What are experimental APIs?

Experimental APIs are normal APIs, that run on our infrastructure, but they haven't met the mark in terms of goal, accuracy, or reliability, according to our team. These APIs may produce outputs that are irrelevant, misleading, or incorrect at times. They are not intended for production environments.

What is the difference between a Developer API token and a regular API token?

Developer API tokens are designed for testing your integration with an API. They allow you to make calls that validate your input and return dummy data in the same format as the live API, so you can test your implementation without using your paid API calls. Normal API tokens are used for live requests. Both token types are passed to the API in the same way.

How can I get support if I run into issues with an API?

If you run into any issues, please use the contact form on our website to get in touch with our support team. We'll get back to you as soon as possible.

Do you provide SDKs for your APIs in different programming languages?

We do not provide language-specific SDKs. However, we do provide basic code examples and OpenAPI specification files to help you get started. Our APIs are platform-agnostic and can be accessed using any language or tool that supports standard REST calls, such as cURL, JavaScript, Python, and more.

Where can I find OpenAPI specification files for your APIs?

OpenAPI specification files are available for each API at `https://infinitode.netlify.app/openapi/api-name/openapi.yaml`. Replace "api-name" with the specific API you're working with. These files can be imported into tools like Postman, Insomnia, or used to generate client libraries in your preferred programming language.

How do I choose between using GET and POST methods?

Both methods are supported, but we recommend POST for most use cases, especially when dealing with complex parameters or sensitive data. GET requests append parameters to the URL, which can cause formatting issues with complicated parameters and may expose sensitive information in server logs. POST requests send parameters in the request body, providing better security and handling of complex data structures.

What's the best practice for handling API errors in my application?

Implement proper error handling by checking HTTP status codes and parsing error messages. Common practices include: implementing retry logic with exponential backoff for temporary errors (like 429 rate limits), logging errors for debugging, gracefully handling different error types, and providing meaningful error messages to end users. Remember that all errors reaching our backend are billable.

Can I make concurrent API calls to improve performance?

Yes, you can make concurrent API calls, but be mindful of rate limits which vary by API and plan. Implement proper throttling to avoid hitting rate limits, which would result in 429 errors and still count toward your billable usage. Check the specific API documentation for rate limit details.

How do I integrate APIs into my business applications?

Start by reviewing the API documentation for your specific use case, then use Developer tokens to test your integration. Once tested, implement proper error handling, security measures (like securing your API tokens), and monitoring. Consider implementing caching where appropriate to optimize performance and reduce API usage.

Are there usage analytics available for my API calls?

Usage statistics and analytics are available in your account dashboard. You can monitor your API usage, track remaining calls, view error rates, and analyze usage patterns to optimize your integration and plan selection.

What happens if I exceed my API rate limits?

If you exceed rate limits, you'll receive a 429 error response. These rate-limited requests are still billable as they reach our backend systems. To avoid this, implement proper rate limiting in your application and consider upgrading your plan if you consistently hit limits. Rate limit specifications are detailed in each API's documentation.

Can I use your APIs for creative projects and applications?

Absolutely! Our APIs are designed to support creative professionals and projects. Whether you're building interactive installations, generative art applications, content creation tools, or innovative user experiences, our APIs provide the flexibility and capabilities needed for creative work. Check our AI APIs for particularly creative applications.

Make sure to properly handle errors when using our APIs. Common errors are listed in each APIs' documentation pages.