https://docs.test.geena.eu/organization-api/index.html Organization API The Partner API is the user’s side of a connection: a token bound to one person reads and fills what that person granted. The Organization API (/org/v1) is your organization’s side: what it already holds — the requests people accepted, the copies it kept, the files it holds for a request, and the update proposals addressed to it — reachable from your own systems with a member-bound token instead of a dashboard session. It is the plane a back office, a CRM sync or a KYC workflow speaks; the dashboard’s organization pages run on exactly the same rules. Hugo en https://docs.test.geena.eu/organization-api/requests/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://docs.test.geena.eu/organization-api/requests/index.html Requests, records & kept copies List your requests GET /org/v1/requests GET /org/v1/requests?email=anna@example.com Every request your organization holds — pending invitations it sent and the connections people accepted — newest first, optionally narrowed to one recipient email (normalized, exact). Metadata only, all of it your own, so the call writes no receipt. Requires request_read. https://docs.test.geena.eu/organization-api/files/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://docs.test.geena.eu/organization-api/files/index.html Request files The files your organization holds for a request come from two directions and live in one listing: kept copies of the person’s files (origin: kept — taken under a keep verb, one version per keep) and files you attached yourself (origin: added — a signed agreement, a letter, a scan of your own). Both are rows of your organization’s own vault carrying the request they belong to; the person sees neither, because no organization → person direction exists. Every route on this page needs request_manage; writes also need the file permission named. https://docs.test.geena.eu/organization-api/proposals/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://docs.test.geena.eu/organization-api/proposals/index.html Update proposals A proposal is a “the source of something you hold has a newer version” notice: the person — or, for a company’s record, whoever edits inside that company — published a new version of a resource your organization holds a copy of, and the request now asks you to decide. On an auto slot the new version is kept without a decision (queued while your key is cold); on a manual slot it becomes a proposal. Every route here needs request_manage. https://docs.test.geena.eu/organization-api/openapi/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://docs.test.geena.eu/organization-api/openapi/index.html OpenAPI specification The /org/v1 plane is defined by an OpenAPI 3.0 document — the same file the Geena backend generates its routing from, so the published contract cannot drift from the implementation. Download org-v1.yaml curl -sO https://docs.test.geena.eu/openapi/org-v1.yaml Generate a typed client from it, or import it into an API tool, exactly as with the partner plane’s document. The same conventions apply: path ids are UUIDs on paper but a malformed one answers the oracle 404 not_found, and the OAuth endpoints that mint the member-bound token are documented under Connect with Geena, not here.