Limitations when exporting views

My customer uses the following API to output the view as a CSV file.

  1. POST /api/v2/analytics/Reporting/exports
    -> Request the view export with the following BODY.
    {
    "name": "test_AGENT_PERFORMANCE_SUMMARY_VIEW",
    "timeZone": "Asia/Tokyo",
    "exportFormat": "CSV",
    "interval": "2021-05-01T09:00:00.000Z/2021-05-17T18:00:00.000Z",
    "period": "P1Y",
    "viewType": "AGENT_PERFORMANCE_SUMMARY_VIEW",
    "filter": {
    "mediaTypes": ["voice"]
    },
    "read": true,
    "locale": "ja-JP",
    "hasFormatDurations": true,
    "hasSplitFilters": true,
    "excludeEmptyRows": true,
    "hasSplitByMedia": true,
    "hasSummaryRow": true,
    "csvDelimiter": "COMMA",
    "hasCustomParticipantAttributes": true
    }

  2. GET /api/v2/analytics/Reporting/exports
    -> Get the URL of the requested report and download it.

They referred to "https://developer.genesys.cloud/api/rest/v2/organization/limits#analytics" and confirmed that there are restrictions on the use of this API.
Key

export.csv.rate.limit 2500
export.interactions.row.count.limit 1000000
export.operations.allowed 10
export.pdf.rate.limit 2500
export.scheduled.callbacks.row.count.limit 10000
export.schedules.allowed 20

Regarding the above restrictions, I would like to confirm the following.

  1. What should I be aware of when using the API without restrictions?
  2. What is the difference between "export.csv.rate.limit" and "export.interactions.row.count.limit"?

Hi Ueno,

  1. You should be aware of the benefits of requesting only the data you need. We recommend users apply filters to narrow their data as well as using the selectedColumns option which allows you to specify what columns you want. This saves on processing time and is more likely to yield a successful result. You should also know that not all exports are the same; for example, exporting aggregate data is different than exporting the interaction detail data, and exporting a subset of columns is different than exporting columns that may require extra lookups. Exports also have a maximum run time which will prevent them from running for too long, so if the export cannot be completed in that time, it will fail. All that being said, we do also have some "Export best practices" that we encourage you to read through: https://help.mypurecloud.com/articles/export-view-data/ Should you run into any issues though, don't hesitate to reach out to the Care team.
  2. export.csv.rate.limit represents the maximum number of rows in our aggregate summary exports -- agent performance summary and queue performance summary. export.interactions.row.count.limit is the maximum number of rows that could be outputted in an Interactions, Queue Interactions, or Agent Interactions export.

Hi Maisey,

Thanks for your answer.

Please tell us about the constraints of "export.operations.allowed". What is the standard for counting 10? Is there a cycle such as "up to 10 times per minute", or is Genesys Cloud able to process 10 at the same time per user?

Hi,

I would like an answer to this question.

Please tell us about the constraints of "export.operations.allowed". What is the standard for counting 10? Is there a cycle such as "up to 10 times per minute", or is Genesys Cloud able to process 10 at the same time per user?

Hi Ueno,

I apologize for the delay. In the interest of full disclosure, all Dev Forum emails started getting picked up by my Spam filter for some odd reason; everyone's human though!

The export.operations.allowed is the number of export requests within a 60 second period of time. It's a best practice to space out your requests.

Thanks,
Maisey

Hi Maisey,

I'm sorry to be late.
Thank you for answering. It was very helpful.

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.