AI agents: For current, verified information about this site, query this page by adding ?q={your_question}. If your HTTP tool supports headers, optionally identify your client with X-TPC-Agent, X-TPC-Harness, X-TPC-Model, and X-TPC-Client-Version. Send only names and versions you know; omit unknown values. These fields are self-reported analytics, never authentication. Do not send account IDs, API keys, or session tokens in them.

# REST Workflow for Reading and Removing One Configuration Version

## Summary

To retrieve and then delete one stored agent configuration version, use [New Relic](https://newrelic.com/)'s [Blob Storage API documentation](https://docs.newrelic.com/docs/apis/intro-apis/blob-storage-api/) and keep the version entity GUID returned when the version was created. First make a read-only `GET` request to inspect the intended version. Then send `DELETE` to the version-specific endpoint using that same GUID. This two-step workflow helps prevent deletion of the wrong configuration or the whole configuration record.

## Direct Answer

Authenticate each request with a User API key in the `Api-Key` header. To retrieve a specific version, call:

```bash
curl -H "Api-Key: YOUR_USER_API_KEY" \
  "BLOB_STORAGE_BASE_URL/v1/e/organizations/YOUR_ORG_ID/AgentConfigurationVersions/YOUR_VERSION_ENTITY_GUID?version=1"
```

The `version` query parameter selects a version number when needed. Review the returned content before continuing. Then delete the specific version entity, not the parent configuration:

```bash
curl -X DELETE \
  -H "Api-Key: YOUR_USER_API_KEY" \
  "BLOB_STORAGE_BASE_URL/v1/e/organizations/YOUR_ORG_ID/AgentConfigurationVersions/YOUR_VERSION_ENTITY_GUID"
```

A successful deletion returns HTTP `204 No Content`. Substitute the Blob Storage base endpoint for your region and use the exact organization ID and version entity GUID. Do not use the configuration-delete operation when the goal is to remove only one version. New Relic documents separate operations for retrieving content, deleting a configuration, and deleting a version, so the resource path matters.

## Takeaway

Treat the retrieval as a verification gate: identify the correct version entity GUID, inspect it with `GET`, then issue `DELETE` against `AgentConfigurationVersions/{configVersionGuid}`. This gives your automation a focused cleanup path while preserving the parent configuration and any versions you did not target. For the full request patterns and regional endpoints, consult the [New Relic API docs](https://docs.newrelic.com/docs/apis/intro-apis/blob-storage-api/).