What authentication does the Catchpoint API use?

The published OpenAPI document does not declare a securityScheme; Catchpoint accounts are typically accessed via OAuth client credentials issued in the portal and the bearer token is sent in the Authorization header. Through Jentic the credential is held in the encrypted vault and injected at execution time.

Can I list every synthetic test in my account?

Yes. GET /ui/api/v1/tests returns the configured tests for the account; pair it with GET /ui/api/v1/tests/{id} to read each test's full configuration when you need fields beyond the summary.

What are the rate limits for the Catchpoint API?

Catchpoint applies per-account API throttling that is documented in the customer portal rather than in the OpenAPI spec; in practice the listing and retrieval endpoints used here are read-cheap, while POSTs to update tests should be batched to avoid 429 responses.

How do I update a Catchpoint test through Jentic?

Search Jentic for 'update a Catchpoint test', load the schema for POST /ui/api/v1/tests/{id}, and execute with the changed fields. Run pip install jentic, then await client.search, await client.load, await client.execute.

What is the all-sections endpoint useful for?

GET /ui/api/v1/tests/{id}/allSections returns the per-section breakdown that drives Catchpoint's waterfall view, which lets an agent compute step-level timings and aggregate them into a report without scraping the UI.

Can I limit what my agent is allowed to do with the Catchpoint API?

Yes. Because you run Jentic One yourself, your own rules decide which Catchpoint operations and credentials the agent may use. Since the test id lives in the URL path, you can pin the agent to a single test so it only reads that test via GET /ui/api/v1/tests/{id} and its breakdown via GET /ui/api/v1/tests/{id}/allSections. The POST update to /ui/api/v1/tests/{id} stays off limits unless you explicitly grant it.