# Propose POST /v1/projects/{project_id}/lifecycle-service-grants Propose Authentication: bearer access token with audience `taifa-management`. Endpoint roles and eligibility are reviewed separately from the OpenAPI bearer scheme. No operation-specific scopes are declared in the OpenAPI document. Bearer authentication and endpoint authorization requirements still apply. ## Parameters | Name | In | Type | Required | Description | | --- | --- | --- | --- | --- | | `project_id` | path | string | Yes | | | `idempotency-key` | header | string | Yes | | ## Request body ### application/json Required; LifecycleServiceProposal | Field | Variant | Type | Required | Description | | --- | --- | --- | --- | --- | | `reason` | | string | Yes | Validation: min length 8; max length 500 | | `issuer` | | string | Yes | Validation: min length 1; max length 2048 | | `subject` | | string | Yes | Validation: min length 1; max length 255 | ## Responses ### 201 Successful Response | Field | Variant | Type | Required | Description | | --- | --- | --- | --- | --- | | `id` | | string | Yes | | | `project_id` | | string | Yes | | | `issuer` | | string | Yes | | | `subject` | | string | Yes | | | `capability` | | lifecycle-consumer | Yes | | | `status` | | pending_review \| effective \| revoked | Yes | | | `active` | | boolean | Yes | | | `version` | | integer | Yes | Validation: minimum 1; maximum 3 | | `proposal_digest` | | string | Yes | Validation: pattern ^[a-f0-9]{64}$ | | `proposer` | | string | Yes | | | `approver` | | string \| null | Yes | | | `proposal_audit_id` | | string | Yes | | | `approval_audit_id` | | string \| null | Yes | | | `revocation_audit_id` | | string \| null | Yes | | | `created_at` | | string ยท date-time | Yes | | | `approved_at` | | string \| null | Yes | | | `revoked_at` | | string \| null | Yes | | ### 422 Validation Error | Field | Variant | Type | Required | Description | | --- | --- | --- | --- | --- | | `detail` | | ValidationError[] | No | | ## Request examples Illustrative only. Replace placeholders and keep management tokens on the server. ### cURL ```sh curl -X POST 'https://YOUR_IDENTITY_HOST/v1/projects/REPLACE_WITH_PROJECT_ID/lifecycle-service-grants' \ -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \ -H 'idempotency-key: REPLACE_WITH_IDEMPOTENCY_KEY' \ -H 'Content-Type: application/json' \ --data '{ "reason": "REPLACE_WITH_REASON", "issuer": "REPLACE_WITH_ISSUER", "subject": "REPLACE_WITH_SUBJECT" }' ``` ### TypeScript (Node.js/server-side) ```typescript const response = await fetch('https://YOUR_IDENTITY_HOST/v1/projects/REPLACE_WITH_PROJECT_ID/lifecycle-service-grants', { method: 'POST', headers: { Authorization: `Bearer ${process.env.TAIFA_MANAGEMENT_TOKEN}`, 'idempotency-key': 'REPLACE_WITH_IDEMPOTENCY_KEY', 'Content-Type': 'application/json' }, body: JSON.stringify({ "reason": "REPLACE_WITH_REASON", "issuer": "REPLACE_WITH_ISSUER", "subject": "REPLACE_WITH_SUBJECT" }) }); const result = await response.json(); ``` ### Python ```python import os import json import requests response = requests.request( 'POST', 'https://YOUR_IDENTITY_HOST/v1/projects/REPLACE_WITH_PROJECT_ID/lifecycle-service-grants', headers={'Authorization': 'Bearer ' + os.environ['TAIFA_MANAGEMENT_TOKEN'], 'idempotency-key': 'REPLACE_WITH_IDEMPOTENCY_KEY'}, json=json.loads('{"reason":"REPLACE_WITH_REASON","issuer":"REPLACE_WITH_ISSUER","subject":"REPLACE_WITH_SUBJECT"}') ) response.raise_for_status() ``` ## Response example No response example in the current specification.