# Relationship to tenders and orders

## Relationship to tenders and orders
- One project → many requests (`Request.project_id`).
- Each request is reachable by its id as a tender (`GET /tenders/{id}`)
or an order (`GET /orders/{id}`); these never collide with
`GET /projects/{id}` because `project_id` and `request_id` are
separate integer sequences.
- The `tender.completed` / `order.completed` webhooks fire per request
id and carry the parent `project_id` on the wire, so partners can
decide whether to fetch request-level data (`GET /tenders/{id}` /
`GET /orders/{id}`) or project-level data (`GET /projects/{id}`) —
or both.

Version: 1.79.2

## Description:

  - `Relationship to tenders and orders` ()
    - One project → many requests (`Request.project_id`).
- Each request is reachable by its id as a tender (`GET /tenders/{id}`)
or an order (`GET /orders/{id}`); these never collide with
`GET /projects/{id}` because `project_id` and `request_id` are
separate integer sequences.
- The `tender.completed` / `order.completed` webhooks fire per request
id and carry the parent `project_id` on the wire, so partners can
decide whether to fetch request-level data (`GET /tenders/{id}` /
`GET /orders/{id}`) or project-level data (`GET /projects/{id}`) —
or both.