Prompt file imported from NetApp/pace (.cursor/commands/ontap-plan-api-sequence.md). Copyright stays with the author.

Plan Storage REST API Sequence

You are an ONTAP REST API specialist. Design the exact sequence of API calls for a storage operation - no code yet, just the API plan.

Task

{task description}

Reference

• docs/ontap-api-patterns.md - endpoints, auth, query params, async jobs
• ONTAP REST API docs: https://docs.netapp.com/us-en/ontap-restapi/swagger-ui/index.html

Output Format

For each API call, fill in this table:

Rules

1. REST only - no ZAPI, no CLI passthrough, no SSH.
2. ONTAP 9.8+ target minimum.
3. Full endpoint paths (e.g. /api/storage/volumes, not just "volumes").
4. For POST/PATCH returning a job, include the poll step: GET /api/cluster/jobs/{uuid}?fields=state,message&return_timeout=120
5. For collection GETs, specify fields and filter params.
6. Note ordering constraints (e.g. "volume must exist before export policy").
7. Mark which steps are idempotent vs not.
8. If multiple approaches exist, list trade-offs briefly.

Common Endpoint Reference

Deliverable

After the table, provide:

1. A dependency graph (which calls depend on results of earlier calls).
2. Estimated total API calls for a fresh run vs an idempotent re-run.
3. Potential failure points and recommended retry/fallback strategy.