# Backup API: return created resources on create endpoints

**Project:** API | **Board:** Planned | **Votes:** 1
**URL:** https://roadmap.ploi.io/projects/6-api-level-requests/items/1543-backup-api-return-created-resources-on-create-endpoints

---

Hi,
I have a small suggestion regarding the backup API.

Currently, both `POST /api/backups/database` and `POST /api/backups/file` return only a success message after creating backup configurations.

Would it be possible to also return the created resource(s), including IDs, in the response?

This should be fully backward compatible, as the existing `message` field can remain unchanged, with the created resource(s) added as an additional field.

For example:

```
{
  "message": "Backup settings have been saved for 2 databases",
  "data": [
    {
      "id": 123,
      "type": "local",
			....
    },
    {
      "id": 124,
      "type": "local",
			....
    }
  ]
}
```

Just a quick follow-up to my previous message about the backup API:
https://roadmap.ploi.io/projects/6-api-level-requests/items/1537-api-ux-improvements-for-backup-management

I wanted to clarify that my main issue would already be solved if the create endpoints returned the created resource(s), including IDs.

One of the key problems I currently face is the need to set `local_path`. Since it is not returned in the create response, I often have to first create the backup, then search for it, and finally perform an update to retrieve or adjust the missing data. 

Another related issue was setting `next_backup_at`, but I noticed this has already been addressed - thanks a lot for that!