Understand Resource ID availability when using the Flexera API

The Flexera API provides usage, cost, and resource-level data. However, Resource ID availability depends on the granularity you select in your API request. Understanding these limits helps you design accurate reports and avoid missing data.

How Resource ID availability works

Resource IDs are only available within specific retention windows. These limits vary based on the granularity used in your request.

Daily granularity

When you use granularity=daily:

• Resource IDs are available for the past 31 days
• Requests outside this window still return data
• Resource ID fields are not included in older results

Monthly granularity

When you use granularity=monthly:

• Resource IDs are available for the past 90 days
• Requests outside this window return aggregated data only
• Resource ID fields are not included in older results

What happens when data exceeds retention limits

If your request exceeds the supported retention period:

• The API still returns usage or cost data
• Data is aggregated at the requested granularity
• Resource ID fields are not populated

How this impacts your reporting

When building reports, automation, or monitoring workflows:

• Account for retention limits when querying historical data
• Avoid relying on Resource IDs for older datasets
• Design pipelines to handle missing Resource ID fields gracefully