Developer
REST API for Your Test Assets and Test Data
Every asset in your TestAssets library is also available over a simple REST API — so your CI jobs, Playwright suites, k6 tests, and internal tools can read the same data your QA team uses by hand.
Why teams choose this
One source of truth
Stop duplicating fixtures between repos. Your tests pull from the same library your QA engineers manage.
Simple API key auth
Generate scoped keys per environment. Rotate without redeploying.
Fast and rate-limited
Built on edge functions with sensible per-endpoint rate limits, so your CI pipelines stay snappy and protected.
Works with anything that speaks HTTP
Playwright, Cypress, k6, Postman, GitHub Actions, custom Bash — if it can curl, it can read your test data.
How it works
- 1
Generate an API key
From Settings → API, create a key for the environment you want to read from.
- 2
Call /assets or /asset-lists
Pass the apikey header. Search and filter by list, tag, or text.
- 3
Use the values in your pipeline
Inject them into env vars, fixtures, or test setup hooks.
Built for teams that...
- Playwright suites pulling staging logins at runtime
- k6 load tests pulling 10,000 sample inputs
- GitHub Actions setting up env vars from a shared list
- Internal admin tools reading sandbox identifiers
Frequently asked questions
Ready to try TestAssets?
Free to get started. No credit card required.
Create your account