Skip to main content
Integrations and API Keys allow external tools like ReportPortal agents, JUnit reporters, and CI/CD pipelines to push test results directly into OneTest. They’re fully compatible with the ReportPortal v2 API.

​
Setting Up

1

Navigate to Settings

Go to Settings > Integrations and API Keys from the sidebar.
2

Create an API Key

Click + Add API Key, give it a name (e.g., “CI Pipeline” or “Staging”), and save. The key is shown only once — copy it immediately.
3

Configure Your Pipeline

Use the generated API key in your CI/CD configuration:
Your Product UUID is displayed on the Integrations and API Keys page and can be copied with one click.
4

Run Tests

Execute your automated tests. Results will automatically appear in your Test Runs dashboard alongside manual test runs.

​
API Endpoints

OneTest provides ReportPortal v2 compatible endpoints:

​
Managing API Keys

Each API key has:
  • Status — Active or expired
  • Retention period — How long test results are kept (default: 90 days)
  • Expiration date — When the key expires
  • Allowed Scopes — Granular permissions controlling which APIs this key can access
  • Last Active — When the key was last used
You can regenerate or delete keys at any time. Deleting a key immediately revokes access for any pipelines using it.
API keys are shown only once when created. Store them securely in your CI/CD secrets (e.g., GitHub Secrets, GitLab CI Variables).

​
JUnit XML Import

For frameworks that don’t support ReportPortal agents, you can import JUnit XML files directly:
Each API call costs 1 coin from your weekly budget. Browser UI usage is always free. See Usage & Billing for details.

​
What’s Next?

View Test Runs

See your automated test results alongside manual runs

Usage & Billing

Monitor API usage and coin consumption