Suppliers, buyers and frameworks

Search directories

Use GET /v1/suppliers or GET /v1/buyers with q, region, limit and offset. Each resource has its own read scope. Retrieve a record with /v1/suppliers/{id} or /v1/buyers/{id} using the UUID returned by search. Detail responses contain identity fields and up to 100 linked notices. tenderPreviewLimit makes this preview boundary explicit. Private relationship scores and raw source metadata are excluded.

Framework agreements

GET /v1/frameworks accepts q, status, type, limit and offset. GET /v1/frameworks/{id} returns the agreement plus buyers, suppliers and call-offs, capped at 100 items per collection. relatedRecordLimit makes that limit explicit. supplierCount and callOffCount describe the wider agreement where available.

Bookmarks

GET /v1/bookmarks lists the key creator's personal tender bookmarks. POST /v1/bookmarks/{id} adds one and DELETE removes it. Bookmark writes are idempotent and need bookmarks:write; listing needs bookmarks:read. Personal bookmarks follow that user across their workspaces, while comments and pipelines remain bound to the key's organisation.

Saved searches

GET /v1/saved-searches and GET /v1/saved-searches/{id} return saved search definitions in the key's organisation with saved-searches:read. The list covers the first 100 saved searches from the same tenant search service used by the app; offset is capped at 99 and nextOffset stops at that boundary. These endpoints do not execute searches or change alert settings. The query object contains the filters stored by the application. Use the tender search endpoint for public API searches.