Available with limitations

Extend clinical research workflows through governed integrations.

A partner should be able to call a scoped API without receiving the audit log or another tenant’s participants. ValidTrials can mint a key once, store only its hash, refuse private webhook addresses, and reject an extension that tries to upload executable code. A sandbox organization accepts only synthetic participant codes. There is no public marketplace of named partners.

What this capability does

Keys

The token is shown once. Scopes named platform, audit or admin are rejected.

Catalog

The listed routes are the ones the key is allowed to know about. Platform and audit paths are omitted.

Webhooks

HTTPS only, and not to a private address. The signing function exists. A finished delivery loop to a customer is not claimed.

Extensions

A manifest may describe a connector. A field named code or script is refused.

Sandbox

Participant codes must start with SYN-.

No fake partners

There is no directory of certified vendors.

How it works

Create a key

An administrator copies it once.

Call

The key can do only its scopes.

Review an extension

A person marks the review state. The software does not run the upload.

Revoke

A revoked key stops working.

Connected modules and services

Questions

Can an extension run Python we upload?

No.

Is there a partner logo wall?

No.

Available with limitations means the described software behavior exists. A professional service is work a person does under a separate scope. Nothing here is a certification.

See the workflow on your protocol.

The conversation is about your study design and what the software can and cannot do today.