# Version 4 of Calls API - includes the campaign name

Retrieving call data just got more insightful when using Retreaver's [API](https://retreaver.github.io/core-api-docs/#v4---calls). Previously, identifying a campaign required a secondary lookup using the campaign_id. With the release of V4, we’ve nested the full campaign object directly within the call response - saving you an extra API hit and providing immediate context.

### The Evolution of the Response

In V1, V2, and V3, the legacy format provided only the  campaign identifier:

```json
{
  "call": {
    "campaign_id": "12345",
  }
}
```

### V4 

The updated format provides both the Campaign ID and the name:

```json
{
  "call": {
    "campaign": {
      "id": "12345",
      "name": "Woof Woof"
  }
}
```

### Should you migrate?

In short: Yes. While we aren't pulling the plug on legacy versions just yet, V4 is where our latest features and performance optimizations live. Moving to V4 now ensures your integration is future-proof and reduces the complexity of your data processing.

**Next Step**: Check out the [Calls V4 Documentation](https://retreaver.github.io/core-api-docs/#v4---calls) to start your upgrade. Most of the JSON response remains unchange making the transition easier.

If you've never used Retreaver API see our [guide on creating API Keys](https://learn.retreaver.com/guides/how-to-use-retreaver-s-api)