If you have saved environments in the project, static
environments use their configured URL and environment-specific credential
overrides. You can copy environment IDs from Project Settings → Test environments
or fetch them with GET /api/v1/projects/{projectId}.For one-off URLs, pass targetUrl. You can also set environment to control how
the run appears in the results list:
production
staging
preview
If you pass targetUrl without environment, the run is marked as preview.
Use environment: "staging" for staging deployment tests.
environment: "staging" only controls the Results environment label. It does
not select a saved environment row or its credential overrides.
Choosing the run platform
Mobile tests are stored without a fixed platform, so the webhook decides which one
to run. Pass platform to choose it:
platform defaults to ios when omitted. An Android batch must set "platform": "android" -
otherwise the run is planned as iOS and any Android mobile app override fails with
InvalidMobileApp / “Selected mobile app was not found for this project”, even though the app
exists in the dashboard.
A group cannot mix iOS and Android tests in one mobile request - split the group
or trigger one platform at a time.
Mobile app override
You can override the app build used by mobile tests in the group. The build must match the requested run platform (ios or android), so send platform alongside the override for Android.By bundle ID - resolves to the latest uploaded app matching that bundle identifier:
Use appId when multiple builds share the same bundle ID and you need to pin a specific upload.For an Android build, the same call with "platform": "android":
For Android, pass "platform": "android" with an .apk artifact - the artifact
extension must match the requested platform.Only one of bundleId, appId, or artifactUrl can be provided per request.
source: "test_default" means each mobile test used its saved app selection.
source: "app_id" means the webhook used an already uploaded project app, selected by bundleId or appId.
source: "artifact_url" means TesterArmy imported the artifact for this batch.
Artifact-imported apps are temporary. They are removed automatically after every run in the webhook batch reaches a terminal state.
Failure notifications
When a webhook-triggered batch completes and any test fails, TesterArmy sends the failure summary to connected chat providers such as Slack or Discord. If no chat provider delivers, TesterArmy falls back to email.Batches triggered with commitSha can still report status back through GitHub, but chat notifications remain project-level alerts for the completed batch.
Limits
1 webhook per group. The secret is shown once. If it is lost, use Regenerate URL in the group’s webhook menu; the previous URL stops working immediately.
Subject to your team’s usage limits - returns 429 if exceeded.
Webhook must be active to accept requests. Switching the webhook Off deactivates it (the URL is preserved); a deactivated webhook returns 403.
Assistant
Responses are generated using AI and may contain mistakes.