api.GetUsageTopAvgMetrics does not parse response properly

[jgulick48]

Describe the bug
A clear and concise description of what the bug is.

When calling api.GetUsageTopAvgMetrics the returned struct does not parse the Metadata data properly. The Metadata is in the raw response and under UnparsedObject but in the returned struct all the Metadata fields are null.

Label the issue properly.

• Add severity/ label.
• Add documentation label if this issue is related to documentation changes.

To Reproduce
Steps to reproduce the behavior:

1. Follow the code example for Go located on https://docs.datadoghq.com/api/latest/usage-metering/?code-lang=go
2. Execute the code in a debug and inspect the returned resp object.
3. Under Metadata all fields will be null and under Unparsed Object, the relevant data will be there.

Expected behavior
Metadata object should be parsed properly.

Screenshots
Code used in my local testing.

func (c *client) GetMetricsUsagePage(ctx context.Context, nextPage string) (UsageTopAvgMetricsResponse, error) { ddctx := c.getAuthContext(ctx) api := datadogV1.NewUsageMeteringApi(c.ddClient) options := datadogV1.NewGetUsageTopAvgMetricsOptionalParameters().WithDay(time.Now().AddDate(0, 0, -2)).WithLimit(5000) if nextPage != "" { options = options.WithNextRecordId(nextPage) } apiResp, r, err := api.GetUsageTopAvgMetrics(ddctx, *options) if err != nil { return UsageTopAvgMetricsResponse{}, err } if metadata, ok := apiResp.Metadata.GetPaginationOk(); ok { lo.G(ctx).Infof("Next Page is: %s", metadata.NextRecordId) } defer r.Body.Close() resp := UsageTopAvgMetricsResponse{} if err := json.NewDecoder(r.Body).Decode(&resp); err != nil { return UsageTopAvgMetricsResponse{}, err } waitForRateLimit(ddctx, r) return resp, nil

Environment and Versions (please complete the following information):
A clear and precise description of your setup:

github.com/DataDog/datadog-api-client-go/v2 v2.52.0
go version go1.25.5 darwin/arm64

Additional context
Add any other context about the problem here.

[github-actions]

Thanks for your contribution!

This issue has been automatically marked as stale because it has not had activity in the last 30 days. Note that the issue will not be automatically closed, but this notification will remind us to investigate why there's been inactivity. Thank you for participating in the Datadog open source community.

If you would like this issue to remain open:

1. Verify that you can still reproduce the issue in the latest version of this project.

2. Comment that the issue is still reproducible and include updated details requested in the issue template.