---
title: "Get the team's currently-effective composed posture"
method: GET
path: "/teams/{team_id}/effective-posture"
tags: ["Postures"]
---

# Get the team's currently-effective composed posture

`GET /teams/{team_id}/effective-posture`

## Request

- Base URL: `https://api.mnemom.ai/v1`
- URL: `https://api.mnemom.ai/v1/teams/{team_id}/effective-posture`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-Mnemom-Api-Key`

Returns the alignment + protection composition currently in effect for the team (assigned posture's body merged with the team's templates and agent exemptions). Authorization: `team_id` is resolved to its owning organization from the DB and the caller must be a member (any role) of that org; a team in an org the caller does not belong to returns the same 404 as a nonexistent team.

## Path parameters

- `team_id` string, required

## Response `200`

Effective posture.

- TeamEffectivePosture: The team's actual posture cascade (GET /v1/teams/{id}/effective-posture). Matches handleGetTeamEffectivePosture exactly: the gathered Platform → Org → Team layers (each null when its cascade source is unset) plus the composed body.
  - `team_id` string, uuid, required
  - `org_id` string, nullable, required
  - `gathered` object, required
    - `platform_default` object, nullable, required: Platform-default posture layer, or null when unset.
    - `org_assigned` object, nullable, required: Org-assigned posture layer, or null when unset.
    - `team_assigned` object, nullable, required: Team-assigned posture layer, or null when unset.
  - `composed` object, required: Composed posture (Platform ⊕ Org ⊕ Team cascade closure).

## Other responses

- `400`: Bad request
- `401`: Authentication required
- `403`: Forbidden
- `404`: Resource not found
- `429`: Rate-limit exceeded. The global per-IP limiter (100 requests/minute, applied to every `/v1/*` route) rejected this request. Back off until the window resets — `Retry-After` carries the cooldown in seconds and `X-RateLimit-Reset` the absolute reset time.
- `500`: Server error — request was well-formed but the server failed to fulfill it. Typically a downstream dependency (DB / RPC / external API) returned an unexpected error.

---

[API](https://skmtc.dev/mnemom/apis/mnemom-api.md) · [All operations](https://skmtc.dev/mnemom/apis/mnemom-api/llms.txt) · [OpenAPI document](https://skmtc.dev/mnemom/apis/mnemom-api/revisions/274b7a6ea182?raw)