Managing Zoho API Credits with the ODBC Driver

Managing Zoho API Credits with the ODBC Driver

The Devart ODBC driver for Zoho is designed to use the minimum number of API credits for operations. However, the exact number of credits consumed depends on various factors, including the type of data you're accessing.

Why Does the API Consume More Credits?

Several factors can lead to additional API credit usage:
  1. Primary key-based field access: Some fields can only be accessed through the primary key, which results in extra API calls if included in the query.
  2. SubForm fields: Zoho requires a separate API call for each row that contains a SubForm field.
  3. Aggregate entities: Fetching related entity data requires additional API calls to retrieve underlying data for each record.
Best Practices to Minimize API Credit Consumption

To reduce the number of API credits used:
  1. Only select the specific fields you need for your operation.
  2. Avoid including SubForm fields in your queries, unless absolutely necessary, as they require additional API calls.
  3. Use filters to limit the data retrieved and make more efficient queries.
By following these best practices, you can optimize your usage of Zoho API credits and keep operations efficient.