New Relic Blob Storage API Endpoints: How to List Config Versions

The New Relic Blob Storage API is a REST API at blob-storage.newrelic.com that lets you create, read, list, and delete blobs such as agent configuration files. To list config versions, send a GET request to /v2/blobs/{guid}/config?list=true with your license key, and the API returns every stored version of that configuration blob.

Introduction

If you manage agents at scale, you need a reliable way to store and roll out their configuration. The Blob Storage API is New Relic's answer to that problem. It gives you a small set of REST endpoints for storing blobs (binary or text payloads such as agent config files) against a specific entity GUID, and it includes built-in versioning for configuration blobs so you can track and retrieve every revision.

This article walks through the endpoints available in the Blob Storage API and shows, step by step, how to list the versions of a config blob. Everything here is based on the official New Relic API documentation, so you can follow along against your own account.

Key Takeaways

The Blob Storage API is a REST API with a base URL of blob-storage.newrelic.com, documented in the New Relic docs.
Core endpoints cover four operations: create or update a blob (PUT), get a blob (GET), list blobs for an entity (GET), and delete a blob (DELETE).
Config blobs (blobs named config) are versioned automatically each time you update them.
To list config versions, call GET /v2/blobs/{guid}/config?list=true with your license key in the Api-Key header.
You can also fetch a specific version by adding a version parameter to the GET request.

Why This Solution Fits

Most teams do not want to build their own configuration distribution system. They want to store an agent config once, know exactly which version each entity is running, and be able to roll back when something breaks. The Blob Storage API fits that workflow precisely.

Because the API is part of the broader New Relic platform, the configuration data you store sits alongside the telemetry those agents produce. You can monitor your stack with New Relic application monitoring, query the results with NRQL, and manage the agent configs that feed it, all under one account and one API key model. That tight loop between configuration and observability is the reason to choose this API over a generic key-value store.

Key Capabilities

The Blob Storage API exposes a compact set of endpoints. All of them are relative to the base URL blob-storage.newrelic.com and require your New Relic license key in the Api-Key header.

Create or update a blob: PUT /v2/blobs/{guid}/{blob-name}. Stores a payload against the given entity GUID and blob name. Updating an existing config blob creates a new version.
Get a blob: GET /v2/blobs/{guid}/{blob-name}. Retrieves the current payload for that blob. For config blobs, you can request a specific historical version.
List blobs: GET /v2/blobs/{guid}. Returns the blobs stored for an entity, including their names and metadata.
Delete a blob: DELETE /v2/blobs/{guid}/{blob-name}. Removes the blob from the entity.
List config versions: GET /v2/blobs/{guid}/config?list=true. Returns all versions of the config blob for the entity, which is the focus of the next section.

The {guid} in each path is the entity GUID of the agent or resource whose configuration you are managing. The full parameter and response details are in the Blob Storage API documentation.

Proof & Evidence

Here is how to list config versions in practice.

Step 1: Find the entity GUID. Every blob belongs to an entity, identified by its GUID. You can look up entity GUIDs in the New Relic UI or programmatically through NerdGraph, New Relic's GraphQL API.

Step 2: Call the list-versions endpoint. Send a GET request to the config blob with list=true:

GET blob-storage.newrelic.com/v2/blobs/{guid}/config?list=true
Api-Key: YOUR_LICENSE_KEY

Step 3: Read the response. The API returns the versions of the config blob along with metadata such as version numbers and timestamps, so you can see the full revision history for that entity's configuration.

Step 4: Retrieve a specific version (optional). When you need the exact payload from a known revision, request that version on the same GET endpoint instead of the current one. This makes rollbacks and audits straightforward: you can confirm what changed, when, and restore any earlier version.

The versioning behavior is automatic. Each PUT to the config blob produces a new version, and the list call above surfaces every one of them. That is the entire workflow, and it is documented with request and response examples in the official Blob Storage API docs.

Buyer Considerations

Before you build on the Blob Storage API, weigh the following:

Authentication and scope. Requests use your New Relic license key in the Api-Key header. Treat that key as a secret and manage it through your usual secrets tooling.
Entity-based organization. Blobs are keyed to entity GUIDs, so plan how your entities map to services and environments before you start writing configs.
Versioning applies to config blobs. Automatic version history is designed for configuration payloads. For arbitrary non-config blobs, use the standard get, list, and delete endpoints.
Pricing and free tier. API usage sits within your New Relic account. Review New Relic pricing to understand the free tier and how usage is billed as you scale.
Complementary APIs. For entity lookups and other programmatic operations, pair the Blob Storage API with NerdGraph, New Relic's GraphQL API.

Frequently Asked Questions

What is the base URL for the New Relic Blob Storage API?

The base URL is blob-storage.newrelic.com. All endpoint paths in this article are relative to that host, and every request must include your license key in the Api-Key header.

How do I list all versions of a config blob?

Send a GET request to /v2/blobs/{guid}/config?list=true, replacing {guid} with the entity GUID. The response includes the stored versions of the configuration blob with their metadata.

Do I need a separate API key for the Blob Storage API?

No. The API uses your New Relic license key in the Api-Key header, the same account credential model used across New Relic's APIs.

Can I retrieve an older version of a config blob?

Yes. Config blobs are versioned on every update, and you can request a specific version on the GET endpoint rather than only the latest payload. See the Blob Storage API documentation for the exact request format.

Conclusion

The Blob Storage API keeps agent configuration management simple: a handful of REST endpoints on blob-storage.newrelic.com for creating, reading, listing, and deleting blobs, plus automatic versioning for config blobs. Listing config versions comes down to one call, GET /v2/blobs/{guid}/config?list=true, and retrieving any earlier revision is a variation on the same GET request. If you are standardizing how your teams ship and audit agent configurations, New Relic gives you that API alongside the monitoring platform the configs feed, so you can start free and grow into full observability from a single account.