---
name: Api Platform Versioning
slug: api-platform-versioning
category: SEO
description: Api Platform Versioning helps evolve Symfony API Platform contracts through deprecation, sunset headers, and path or header strategies. Use it when changing resources, DTOs, validation, or security without breaking clients.
github: "https://github.com/dev-toolings/superpowers-symfony/tree/main/skills/api-platform-versioning"
language: TypeScript
stars: 208
forks: 20
install: "npx degit https://github.com/dev-toolings/superpowers-symfony/tree/main/skills/api-platform-versioning ~/.claude/skills/api-platform-versioning"
installs_to: ~/.claude/skills/api-platform-versioning
source_path: skills/api-platform-versioning/SKILL.md
collection_size: 23
category_size: 181
collection_url: "https://dirskills.com/collections/dev-toolings/superpowers-symfony"
added: 2026-09-04T05:27:04.738Z
last_synced: 2026-09-04T05:27:04.738Z
canonical_url: "https://dirskills.com/skills/api-platform-versioning"
---

# Api Platform Versioning

Api Platform Versioning helps evolve Symfony API Platform contracts through deprecation, sunset headers, and path or header strategies. Use it when changing resources, DTOs, validation, or security without breaking clients.

**Install:**

```bash
npx degit https://github.com/dev-toolings/superpowers-symfony/tree/main/skills/api-platform-versioning ~/.claude/skills/api-platform-versioning
```

## README

# Api Platform Versioning (Symfony)

## Use when
- Designing or evolving API Platform contracts and operations.
- Aligning serialization, validation, and security behavior.

## Default workflow
1. Define operation-level contract and payload boundaries.
2. Implement resource/DTO/provider/processor changes with explicit mapping.
3. Apply operation-specific validation and security constraints.
4. Validate functional behavior across happy and negative paths.

## Guardrails
- Keep API contract explicit and version-aware.
- Avoid exposing internal entity fields implicitly.
- Prevent drift between docs and actual serialization.

## Progressive disclosure
- Use this file for execution posture and risk controls.
- Open references when deep implementation details are needed.

## Output contract
- API artifacts changed (resource/DTO/provider/processor).
- Contract/security decisions and rationale.
- Functional verification results.

## References
- `reference.md`
- `docs/complexity-tiers.md`