[GH-ISSUE #219] (Re-)import aliases for batch update of description and recipient #763

Closed
opened 2026-03-14 10:31:05 +03:00 by kerem · 1 comment
Owner

Originally created by @xanoni on GitHub (Oct 22, 2021).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/219

I noticed that aliases can be exported as CSV in the settings.

Is there a way to delete all current aliases and re-import them from the same CSV format?

This would make it much easier to fix things like the format of the alias descriptions.

I haven't seen an import function, so in absence thereof I guess the best I could do is to request all aliases via GET api/v1/aliases and then update each of them individually via PATCH api/v1/aliases/{id}?

I would still encourage implementation of an import function, given many users are probably not super technical.

API:
https://app.anonaddy.com/docs/#get-all-aliases
https://app.anonaddy.com/docs/#update-a-specific-alias

Originally created by @xanoni on GitHub (Oct 22, 2021). Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/219 I noticed that aliases can be exported as CSV in the settings. Is there a way to delete all current aliases and re-import them from the same CSV format? This would make it much easier to fix things like the format of the alias descriptions. I haven't seen an import function, so in absence thereof I guess the best I could do is to request all aliases via `GET api/v1/aliases` and then update each of them individually via `PATCH api/v1/aliases/{id}`? I would still encourage implementation of an import function, given many users are probably not super technical. **API:** https://app.anonaddy.com/docs/#get-all-aliases https://app.anonaddy.com/docs/#update-a-specific-alias
kerem closed this issue 2026-03-14 10:31:10 +03:00
Author
Owner

@xanoni commented on GitHub (Oct 22, 2021):

So to be specific, what I'm trying to achieve is to at least update the "Description" fields via some regex / sed filter.

What would be nice is to then also update the forwarding addresses based on what's in the updated description.

For that, I assume I would use POST api/v1/alias-recipients (in the absence of the import function that I'm asking about above).

API:
https://app.anonaddy.com/docs/#update-recipients-for-a-specific-alias

<!-- gh-comment-id:949249481 --> @xanoni commented on GitHub (Oct 22, 2021): So to be specific, what I'm trying to achieve is to at least update the "Description" fields via some regex / `sed` filter. What would be nice is to then also update the forwarding addresses based on what's in the updated description. For that, I assume I would use `POST api/v1/alias-recipients` (in the absence of the import function that I'm asking about above). **API:** https://app.anonaddy.com/docs/#update-recipients-for-a-specific-alias
Sign in to join this conversation.
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/anonaddy#763
No description provided.