Analytics Aggregates: Handling 'interval' field type mismatch in Pulumi TS

• Env: Genesys Cloud EU West, Pulumi 3.92.0, TypeScript 4.9
• Auth: Service Account (Client Credentials)
• Endpoint: POST /api/v2/analytics/conversations/aggregates
• Error: 400 Bad Request - Invalid value for 'interval'

Can anyone clarify why the Analytics API rejects my interval configuration when deployed via Pulumi?

I’m building a custom interval report to track queue handle times. The Pulumi genesyscloud provider maps the genesyscloud_analytics_view resource to the underlying REST API. When I define the interval block, the generated JSON payload looks correct, but the API returns a 400.

Here is the Pulumi TS snippet:

const customIntervalReport = new genesyscloud.analyticsView("custom-interval-report", {
 name: "Queue Handle Time - Custom Intervals",
 type: "conversation",
 groupBy: ["queue.id"],
 filter: {
 type: "interval",
 interval: {
 type: "custom",
 custom: {
 intervals: [
 { start: "2023-01-01T00:00:00Z", end: "2023-01-01T08:00:00Z" },
 { start: "2023-01-01T08:00:00Z", end: "2023-01-01T16:00:00Z" }
 ]
 }
 }
 },
 metrics: ["handleTime"]
});

The Pulumi preview shows the resource creation, but the apply fails with:
Error creating Analytics View: 400 Bad Request { "errors": [ { "message": "Invalid value for 'interval'", "field": "filter.interval.custom.intervals" } ] }

I’ve verified the ISO 8601 timestamps are valid. I also tested the equivalent JSON payload directly against the /api/v2/analytics/conversations/aggregates endpoint using Postman, and it works fine. The issue seems specific to how the Pulumi provider serializes the filter object or validates the interval type schema.

Is there a known issue with the genesyscloud provider handling custom interval arrays in the filter block? Or am I missing a required nested property like unit or resolution in the Pulumi resource definition? The docs are sparse on custom interval constraints for IaC.

TL;DR: The Analytics API expects ISO 8601 duration strings for the interval field, not numeric values.

You might want to look at using the PureCloudPlatformClientV2.AnalyticsApi SDK to generate the correct payload structure instead of constructing it manually in TypeScript.

const body = new platformClient.AnalyticsApi().createAggregateBody({
 interval: 'PT1H', // ISO 8601 duration
 dateFrom: '2023-10-01T00:00:00Z',
 dateTo: '2023-10-02T00:00:00Z'
});

If you check the docs, they mention the interval field strictly requires ISO 8601 duration strings like ‘PT1H’.

The point above is correct on the format.

You must ensure your Pulumi template serializes this value as a string, not a number, to avoid the 400 error.

The way I solve this is by forcing the interval to a string literal in the Pulumi stack config to prevent TypeScript type coercion.

const interval = 'PT15M'; // Explicit string, never number

Note: Verify your service account has analytics:conversation:read scope.

This happens because the strict schema validation on the POST endpoint, which rejects non-string types for the interval parameter. While the previous suggestions correctly identify the ISO 8601 requirement, the root cause in your Pulumi deployment is likely TypeScript type coercion during the JSON serialization process.

In my Angular enterprise desktop applications, I enforce explicit string typing to prevent this exact issue when constructing API payloads via the PureCloudPlatformClientV2 SDK. You must ensure your Pulumi resource definition explicitly casts the value to a string before passing it to the createAggregateBody method.

// Explicit cast to prevent TS coercion to number
const aggregateBody = {
 interval: String('PT1H'), // Forces string type
 dateFrom: '2023-10-01T00:00:00.000Z',
 dateTo: '2023-10-02T00:00:00.000Z'
};

Verify your service account possesses the analytics:conversation:read scope. Without this, the API may return ambiguous 400 errors. I recommend logging the raw JSON payload sent by Pulumi to confirm the interval field is not being serialized as an integer.