# Delete backup schedule

`DELETE /backup-schedules/{schedule_id}`

:::code-group
```shellscript title="curl"
curl -sS -o /dev/null -w "%{http_code}\n" -X DELETE \
  "https://api.pinecone.io/backup-schedules/${SCHEDULE_ID}" \
  -H "api-key: ${PINECONE_API_KEY}" \
  -H "X-Pinecone-Api-Version: 2026-04"
```
:::

:::code-group
```title="curl"
204
```
:::

:::callout{intent="note"}
This endpoint requires `X-Pinecone-Api-Version: 2026-04`.
:::

Delete a backup schedule. This does **not** delete any backups that were previously created by the schedule.

### Path parameters

- `schedule_id` (string, required) — The ID of the backup schedule to delete.

```shellscript
curl -sS -o /dev/null -w "%{http_code}\n" -X DELETE \
  "https://api.pinecone.io/backup-schedules/${SCHEDULE_ID}" \
  -H "api-key: ${PINECONE_API_KEY}" \
  -H "X-Pinecone-Api-Version: 2026-04"
```

```
204
```

Was this page helpful?

## Related pages

- [Create backup schedule](./database-2026-07-control-plane-create-backup-schedule.md)
- [List backup schedules](./database-2026-07-control-plane-list-backup-schedules.md)
- [Describe backup schedule](./database-2026-07-control-plane-describe-backup-schedule.md)
- [Update backup schedule](./database-2026-07-control-plane-update-backup-schedule.md)
- [Delete backup schedule](./database-2026-07-control-plane-delete-backup-schedule.md)
- [List backup schedule history](./database-2026-07-control-plane-list-backup-schedule-history.md)
- [Create backup schedule](./database-2026-04-control-plane-create-backup-schedule.md)
- [List backup schedules](./database-2026-04-control-plane-list-backup-schedules.md)
- [Describe backup schedule](./database-2026-04-control-plane-describe-backup-schedule.md)
- [Update backup schedule](./database-2026-04-control-plane-update-backup-schedule.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.