API and Resource Unit Consumption
API and Resource Unit Consumption

API and Resource Unit Consumption

Haven OnDemand tracks usage in two ways:

  • Resource Units track usage of static resources, such as text indexes, which reside in the Haven OnDemand system.
  • API Units track usage of APIs.

Static Resource Units

Connector Resource Types

Each Connector flavor uses one static resource unit, which is the unit cost for creating the connector and storing the configuration.

In addition, Connector resources are subject to quota limitations. For more information, see Rate Limiting, Quotas, Data Expiry, and Maximums and the Connector flavor documentation (for a list of flavors, see Connectors).

Text Index Resource Types

Text indexes use static resource units based on the flavor type, and the amount of data.

Each text index flavor has a static resource unit cost, which is the cost for each index component, determined by the maximum index size and specialization. When a text index exceeds the quota size for the index component, Haven OnDemand creates a new component for the text index, up to your total available units. You can also create additional text indexes up to your total available units.

For more information about the different flavors, see Index Flavors.

You can view the total units for your account on the Account Management Quotas page.

Flavor type Maximum index size for each component Static resource unit cost for each component
Standard 10 GB 10
Explorer 200 MB 1
Jumbo 40 GB 20
Custom Fields 10 GB 12
Query Manipulation 500 MB 12
Categorization 1 GB 15

Prediction Model Resources

Each prediction model uses one static resource unit, which is the cost for creating and storing a prediction model.

Query Profile Resource Types

Query Profile resources do not have a resource unit cost, but they are subject to quota limitations. For more information, see Query Manipulation Limits and Rate Limiting, Quotas, Data Expiry, and Maximums.

API Units

For most APIs, usage is tracked for each call. For resource-intensive APIs, such as Speech Recognition and OCR Document, the API usage depends on the amount of data to process, as well as the number of calls that you make.

You can view your API usage on the Account Management Quotas page.

API API Units
List Resources, Index Status, Connector Status No API unit cost
Speech Recognition 1 API unit for every two seconds of audio
OCR Document 1 API unit for each page
Expand Container 1 API unit for every 100 MB
Search API calls against user text indexes No API cost unit incurred
All other APIs 1 API unit per call
APIs that accept multiple inputs with discrete results consume 1 API unit for each input