Data Export FAQ

Other qTest APIs, such as the qTest Manager APIs, focus on automating qTest operations, such as creating test runs or updating defects. When you query the data using qTest native APIs, it only retrieves the current state of your qTest data.

qTest Data Export is a SaaS solution that delivers your qTest data in its raw form. This includes your current and future data, even back to your first day with qTest. The raw data gives you complete control. You can create joins, aggregate the data, create views, and further analyze your data with your preferred BI tools.

We deliver your data in parquet files of CRUD operations to keep your downloads small and fast.

To request an API key, reach out to your CSM or contact support (link opens in a new tab).

Data Export exports 42 qTest database tables, which contain complete information from Insights reports and Explore Data. It also includes integration and custom field data.

Data export doesn't support attachments over 21KB or Session data, such as recorded screen capture.

Once a day, Data Export sends an daily delta update that includes all updated records from the previous calendar day.

Have your developers set up an automated system to download and apply daily delta updates to your data. Ensure they build in a retry for data downloads. If an automated download fails because a file is not present by mid-morning, contact Tricentis Support.

Here's your data timeline in UTC:

• 0:00 UTC: Data cut-off for daily delta updates. Only data from the previous day is included.

• 5:00 UTC: Daily file export starts.

• 6:00 UTC: Typically when daily files finish. Larger datasets may complete as late as 9:30 UTC.

• 7:00 UTC: We suggest you schedule your refresh or ingestion jobs no later than this time.

See the table below for approximate local times of data delivery:

No. Data Export is designed for ongoing replication into a customer-managed data warehouse or data lake while you continue to use qTest. It can't be used as an offboarding, archive, or one-time backup mechanism.

See Is Data Export right for your use case? for more information on supported scenarios and alternative tools.

Allow 2 to 4 weeks from the date your request is submitted. We process requests in the order received. After onboarding begins, it typically takes 2 to 5 days to process your historical data, depending on your data volume.

Your account administrator will receive an email after the full initial export of your data finishes.

See Subscribe to Data Export for the full timeline.

We don't send any email updates. We'll only send one email at the start, to let your qTest account administrator know that we've uploaded your historical data.

Once onboarding is complete, it will take up to 48 hours to upload your historical data.

The standard onboarding timeline is 2 to 4 weeks from the date you submit your request. If onboarding hasn't started after 4 weeks, contact Tricentis Support (opens in a new tab). 

Your data updates asynchronously. The daily data cutoff is midnight UTC, and changes made after midnight UTC appear in the following day's export.

If you're missing changes that are older than 24 hours, contact Tricentis Support (link opens in a new tab).

Daily files are typically available by 5:30 to 6:00 UTC, but they may be available as late as 9:30 UTC. We recommend that you build a retry into your automated download pipeline. If a file is not present by mid-morning, contact Tricentis Support (link opens in a new tab).

A platform incident may prevent delta files from being generated, and affected data may be permanently lost. Check the Tricentis Status Page (opens in a new tab) to see if platform incidents on occurred on the missing dates.

Contact Tricentis Support (link opens in a new tab) immediately if you suspect an incident affected your data.

Certain timestamp fields, such as createddate, lastmodifieddate, creatorid, and lastmodifieduserid, may export as NULL in the initial load. These fields will receive correct values in a later update. If values don't appear after several days, contact Tricentis Support (link opens in a new tab).

This issue affects the following tables:

• builds

• defects

• test_cycles

• test_case_run

• project_modules

• test_suites

Verify that you meet all authentication requirements. Also, ensure that you're not using SSO, which isn't supported.

If you meet all requirements but the error persists, contact Tricentis Support (link opens in a new tab). We'll validate or regenerate your API key.

Contact Tricentis Support (link opens in a new tab) with your ClientID and the affected table name.

Contact Tricentis Support (link opens in a new tab) to request a data size estimate. Re-activating Data Export re-runs the full point-in-time snapshot load, which can significantly increase storage use.