API reference

Search companies

GET /api/v1/search · Catalogue

Operation ID searchCompanies — the stable name a generated client uses for this call.

Full-text search over CROs and CDMOs by what they do, where, and by name, with the same vocabulary as the site. Each result carries the claims that matched and their source ids. Results are paged with a cursor.

Example request

curl --fail-with-body 'https://physicalvalidation.com/api/v1/search?q=bioanalysis&country=NL&limit=2'

Response schema

Every response is the { data, next_cursor, meta } envelope. data is an array; each item has:

Example response

{
  "data": [
    {
      "id": "provider:qps",
      "name": "QPS",
      "uri": "physical-validation://company/provider:qps",
      "url": "https://physicalvalidation.com/company/provider:qps",
      "level": "profiled",
      "match": "exact",
      "providerType": "CRO",
      "websites": [
        "https://www.qps.com"
      ],
      "countries": [
        "NL"
      ],
      "sites": 1,
      "matched": [
        {
          "kind": "service",
          "label": "Bioanalysis",
          "scope": "facility",
          "basis": "published",
          "facilityId": "qps-groningen",
          "sourceIds": [
            "s1"
          ]
        }
      ]
    }
  ],
  "next_cursor": "eyJ2IjoxLCJhZnRlciI6InByb3ZpZGVyOnFwcyJ9",
  "meta": {
    "source_urls": [],
    "generated_at": "2026-10-16T00:00:00.000Z",
    "total": 1,
    "match": "exact"
  }
}

Errors

On an error the body is { error: { code, message, retryable } }. Match on the stable code below, not on the message. A status that can carry either of two codes lists both.

Get a company

GET /api/v1/companies/{id} · Catalogue

Operation ID getCompany — the stable name a generated client uses for this call.

One company: its sites, published claims with scope, basis and sources, and facts read from its own website, each with the page it came from.

Example request

curl --fail-with-body 'https://physicalvalidation.com/api/v1/companies/provider%3Aqps'

Response schema

Every response is the { data, next_cursor, meta } envelope. data has:

Example response

{
  "data": {
    "id": "provider:qps",
    "name": "QPS",
    "uri": "physical-validation://company/provider:qps",
    "url": "https://physicalvalidation.com/company/provider:qps",
    "level": "profiled",
    "providerType": "CRO",
    "websites": [
      "https://www.qps.com"
    ],
    "sites": [
      {
        "id": "qps-groningen",
        "name": "QPS Groningen",
        "uri": "physical-validation://facility/qps-groningen",
        "url": "https://physicalvalidation.com/facility/qps-groningen",
        "location": {
          "city": "Groningen",
          "country": "Netherlands",
          "countryCode": "NL"
        }
      }
    ],
    "claims": [
      {
        "kind": "service",
        "label": "Bioanalysis",
        "scope": "facility",
        "basis": "published",
        "facilityId": "qps-groningen",
        "sourceIds": [
          "s1"
        ]
      }
    ],
    "sources": [
      {
        "id": "s1",
        "title": "QPS — Bioanalysis",
        "url": "https://www.qps.com/bioanalysis",
        "checkedAt": "2026-09-30"
      }
    ],
    "notice": "Claims come from published sources and keep their scope."
  },
  "next_cursor": null,
  "meta": {
    "source_urls": [
      "https://www.qps.com/bioanalysis"
    ],
    "generated_at": "2026-10-16T00:00:00.000Z"
  }
}

Errors

On an error the body is { error: { code, message, retryable } }. Match on the stable code below, not on the message. A status that can carry either of two codes lists both.

List a company's sites

GET /api/v1/companies/{id}/sites · Catalogue

Operation ID listCompanySites — the stable name a generated client uses for this call.

The lab sites of one company, each with its location and resource uri.

Example request

curl --fail-with-body 'https://physicalvalidation.com/api/v1/companies/provider%3Aqps/sites'

Response schema

Every response is the { data, next_cursor, meta } envelope. data is an array; each item has:

Example response

{
  "data": [
    {
      "id": "qps-groningen",
      "name": "QPS Groningen",
      "uri": "physical-validation://facility/qps-groningen",
      "url": "https://physicalvalidation.com/facility/qps-groningen",
      "location": {
        "city": "Groningen",
        "country": "Netherlands",
        "countryCode": "NL"
      }
    }
  ],
  "next_cursor": null,
  "meta": {
    "source_urls": [],
    "generated_at": "2026-10-16T00:00:00.000Z"
  }
}

Errors

On an error the body is { error: { code, message, retryable } }. Match on the stable code below, not on the message. A status that can carry either of two codes lists both.

Get a site

GET /api/v1/sites/{id} · Catalogue

Operation ID getSite — the stable name a generated client uses for this call.

One lab site: location, company, published claims with their sources, and what is unknown.

Example request

curl --fail-with-body 'https://physicalvalidation.com/api/v1/sites/qps-groningen'

Response schema

Every response is the { data, next_cursor, meta } envelope. data has:

Example response

{
  "data": {
    "id": "qps-groningen",
    "name": "QPS Groningen",
    "uri": "physical-validation://facility/qps-groningen",
    "url": "https://physicalvalidation.com/facility/qps-groningen",
    "company": {
      "id": "provider:qps",
      "name": "QPS",
      "uri": "physical-validation://company/provider:qps",
      "website": "https://www.qps.com"
    },
    "providerType": "CRO",
    "location": {
      "city": "Groningen",
      "country": "Netherlands",
      "countryCode": "NL"
    },
    "claims": [
      {
        "kind": "service",
        "label": "Bioanalysis",
        "scope": "facility",
        "basis": "published",
        "sourceIds": [
          "s1"
        ]
      }
    ],
    "unknowns": [],
    "sources": [
      {
        "id": "s1",
        "title": "QPS — Bioanalysis",
        "url": "https://www.qps.com/bioanalysis",
        "checkedAt": "2026-09-30"
      }
    ],
    "checkedAt": "2026-09-30",
    "notice": "Claims come from published sources and keep their scope."
  },
  "next_cursor": null,
  "meta": {
    "source_urls": [
      "https://www.qps.com/bioanalysis"
    ],
    "generated_at": "2026-10-16T00:00:00.000Z"
  }
}

Errors

On an error the body is { error: { code, message, retryable } }. Match on the stable code below, not on the message. A status that can carry either of two codes lists both.

List services

GET /api/v1/services · Vocabulary

Operation ID listServices — the stable name a generated client uses for this call.

The service vocabulary — the capability terms the catalogue uses. Use a slug or label as a service filter on search.

Example request

curl --fail-with-body 'https://physicalvalidation.com/api/v1/services'

Response schema

Every response is the { data, next_cursor, meta } envelope. data is an array; each item has:

Example response

{
  "data": [
    {
      "slug": "bioanalysis",
      "name": "bioanalysis",
      "labels": [
        "Bioanalysis"
      ],
      "role": "research"
    }
  ],
  "next_cursor": null,
  "meta": {
    "source_urls": [],
    "generated_at": "2026-10-16T00:00:00.000Z"
  }
}

Errors

On an error the body is { error: { code, message, retryable } }. Match on the stable code below, not on the message. A status that can carry either of two codes lists both.

List techniques

GET /api/v1/techniques · Vocabulary

Operation ID listTechniques — the stable name a generated client uses for this call.

The technique vocabulary.

Example request

curl --fail-with-body 'https://physicalvalidation.com/api/v1/techniques'

Response schema

Every response is the { data, next_cursor, meta } envelope. data is an array; each item has:

Example response

{
  "data": [
    {
      "slug": "lipid-nanoparticle",
      "name": "lipid nanoparticle",
      "labels": []
    }
  ],
  "next_cursor": null,
  "meta": {
    "source_urls": [],
    "generated_at": "2026-10-16T00:00:00.000Z"
  }
}

Errors

On an error the body is { error: { code, message, retryable } }. Match on the stable code below, not on the message. A status that can carry either of two codes lists both.

List countries

GET /api/v1/countries · Vocabulary

Operation ID listCountries — the stable name a generated client uses for this call.

Countries that have listed sites, with the number of sites in each.

Example request

curl --fail-with-body 'https://physicalvalidation.com/api/v1/countries'

Response schema

Every response is the { data, next_cursor, meta } envelope. data is an array; each item has:

Example response

{
  "data": [
    {
      "code": "NL",
      "name": "Netherlands",
      "count": 12
    }
  ],
  "next_cursor": null,
  "meta": {
    "source_urls": [],
    "generated_at": "2026-10-16T00:00:00.000Z"
  }
}

Errors

On an error the body is { error: { code, message, retryable } }. Match on the stable code below, not on the message. A status that can carry either of two codes lists both.

Prepare a request

POST /api/v1/requests/prepare · Requests

Operation ID prepareRequest — the stable name a generated client uses for this call.

Places a sourcing request draft with the site's vocabulary and returns a review link on physicalvalidation.com where a person adds contact details and sends it. It only drafts: nothing is stored or sent, and no request reaches a provider — so Try it is safe to run.

Request body

{
  "title": "GMP peptide, 50 g",
  "services": [
    "peptide synthesis"
  ],
  "quality": [
    "GMP"
  ],
  "quantity": {
    "value": 50,
    "unit": "g"
  }
}

Example request

curl --fail-with-body 'https://physicalvalidation.com/api/v1/requests/prepare' \
  -H 'Content-Type: application/json' \
  -d '{"title":"GMP peptide, 50 g","services":["peptide synthesis"],"quality":["GMP"],"quantity":{"value":50,"unit":"g"}}'

Response schema

Every response is the { data, next_cursor, meta } envelope. data has:

Example response

{
  "data": {
    "submitted": false,
    "review": {
      "url": "https://physicalvalidation.com/request#…",
      "label": "Review and send on physicalvalidation.com"
    },
    "draft": {
      "title": "GMP peptide, 50 g",
      "services": [
        "Peptide synthesis"
      ],
      "quality": [
        "GMP"
      ]
    },
    "missing": [
      {
        "path": "description",
        "ask": "What should the provider do?"
      }
    ],
    "notice": "Nothing was stored or sent."
  },
  "next_cursor": null,
  "meta": {
    "source_urls": [],
    "generated_at": "2026-10-16T00:00:00.000Z"
  }
}

Errors

On an error the body is { error: { code, message, retryable } }. Match on the stable code below, not on the message. A status that can carry either of two codes lists both.

Start a no-login request

POST /api/v1/unvetted-requests · Intake

Operation ID startUnvettedRequest — the stable name a generated client uses for this call.

Stores a request and emails a 6-digit code to confirm the address — no account needed. The response is identical for any email, so nothing is enumerable, and nothing else runs: no model, crawl or provider contact. These two endpoints return a bare object, not the read envelope.

Request body

{
  "text": "We need GLP bioanalysis for a 12-subject PK study.",
  "email": "you@example.com"
}

Example request

curl --fail-with-body 'https://physicalvalidation.com/api/v1/unvetted-requests' \
  -H 'Content-Type: application/json' \
  -d '{"text":"We need GLP bioanalysis for a 12-subject PK study.","email":"you@example.com"}'

Response schema

This endpoint returns a bare object (not the read envelope):

Example response

{
  "id": "unv_0123456789abcdef0123456789abcdef",
  "status": "code_sent"
}

Errors

On an error the body is { error: { code, message, retryable } }. Match on the stable code below, not on the message. A status that can carry either of two codes lists both.

Verify a no-login request

POST /api/v1/unvetted-requests/{id}/verify · Intake

Operation ID verifyUnvettedRequest — the stable name a generated client uses for this call.

Confirms a request by entering the emailed code, within a 10-minute window and an attempt cap. Idempotent.

Request body

{
  "code": "123456"
}

Example request

curl --fail-with-body 'https://physicalvalidation.com/api/v1/unvetted-requests/unv_0123456789abcdef0123456789abcdef/verify' \
  -H 'Content-Type: application/json' \
  -d '{"code":"123456"}'

Response schema

This endpoint returns a bare object (not the read envelope):

Example response

{
  "status": "received"
}

Errors

On an error the body is { error: { code, message, retryable } }. Match on the stable code below, not on the message. A status that can carry either of two codes lists both.