# Which workspace a bio page is in, for a link that names no workspace

For an old link (`/links/bio/<id>`, an email from before
workspace URLs), so the app can send the tab to
`/links/w/<slug>/bio/<id>`. It works across the caller's
workspaces: the token may be for any of them.

It answers only when Links would let the caller read the bio page in
its own workspace: they are a member with a product seat, Links is
on there, and they own the page (bio pages are owner-only).

Every other case gets the same 404, byte for byte: no such bio page,
one the caller can't read, Links turned off there, a record from
before workspaces, a malformed id, or a request made with an API key
or an OAuth grant (those are bound to one workspace by consent). Both
answers are `Cache-Control: no-store`. Rate-limited per user and per
client IP (the edge's CF-Connecting-IP), one limit across the three
locate routes.


Canonical: https://easerix.com/docs/developers/api/links/bio/locateBioPage

{/* This file was generated by Fumadocs. Do not edit this file directly. Any changes should be made by running the generation command again. */}

export default function Layout(props) {
  const { APIPage, OpenAPIPage } = props.components ?? {};
  // "APIPage" is the old name from v10, this allows both for backward compatibility
  const Comp = OpenAPIPage ?? APIPage;
  return (
    <>
      {props.children}
      <Comp document="links" operations={[{"path":"/v1/bio/{id}/locate","method":"get"}]} />
    </>
  );
}