Lookup DDS

Look up a DDS by identifiers TRACES issued, in one of two forms:

  • internal_reference — OUR OWN filing, identified by the internal reference number assigned at submit. Resolved against the caller's orgs before any TRACES call — an internal reference that doesn't resolve locally never reaches TRACES. Response carries a best-effort live overview and verifyDeclaration verdict; either may be null if TRACES is briefly unreachable — the resolved filing is still a useful answer without them.
  • reference_number + verification_number — a third party's DDS. There is nothing to org-scope and nothing to fall back to, so the response is the bare verifyDeclaration verdict only — no overview, no statement, no geometry — and an unreachable/rejected TRACES fails the request (502/503) rather than returning a half-empty 200.

A body must use exactly one form; mixing both is a 400.

Scope

Gated on eudr:verify, distinct from eudr:read — this endpoint resolves arbitrary reference/verification numbers that fm-api's data cannot org-scope, so a read-scoped key does not reach it by default.

Rate limit

A fixed, tighter allowance (20 requests/minute) applies to this route independent of the caller's normal org allowance, to bound how fast a key can probe identifiers.

Errors

StatusCodeWhen
400BAD_REQUESTBody mixes both forms, or matches neither
401UNAUTHORIZEDMissing/invalid API key
403FORBIDDENKey lacks eudr:verify
404NOT_FOUNDinternal_reference form: nothing resolves for the caller's orgs
502TRACES_REQUEST_REJECTEDidentifiers form: TRACES answered with an authoritative fault
503TRACES_UNAVAILABLEidentifiers form: TRACES could not be reached