Updated August 21, 2026

Rev-Trac

Rev-Trac talks to Velo over the same REST API as any other machine client. There is no engine-native wrapper.

What you need

  • A Velo API key (Settings → API Keys)
  • API origin https://api.velo.aster.pro
  • A suite uploaded with the correct image (robot-sap, robot-web, or playwright)

Flow

  1. Authorization: Bearer velo_... on every request.
  2. POST /suites if the suite is not already uploaded (engine, optional engine_version).
  3. POST /executions with suite_id, strategy, optional filter, variables, callback_url.
  4. Poll GET /runs/{id} or subscribe to callback_url when the execution reaches a terminal status.
  5. Download artifacts from the absolute URLs in artifact_urls (same Bearer token). Follow links.api / links.web on the execution, run, and suite. Related keys on links (suite, runs, tests, archive) point at the API; suite_web is the dashboard. links.runs is GET /executions/{id}/runs.

Dashboard JWTs are accepted but intended for the browser session. Integrators should use an API key.

Related