Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Use mailing_list_id as label in /characters/{character_id}/mail/ #877

Open
antihax opened this issue Apr 24, 2018 · 2 comments
Open

Comments

@antihax
Copy link
Contributor

antihax commented Apr 24, 2018

Feature request

Allow mailing_list_id as a label to /characters/{character_id}/mail/ so we can filter to just mails received on a mailing list to allow easier real time access to mailing list mails.

Also add the Trash mailbox to the API.

Route

/characters/{character_id}/mail/

Authentication

Yup

Use case

Seamlessly filter mail headers to mailing lists like we can with Inbox, Corp, Alliance, etc.

Example returns

Same as current, but filtered to mailing_list_id

image

@antihax
Copy link
Contributor Author

antihax commented Apr 26, 2018

FYI trying to replicate the in game representation of mails in external client.

The "Concord LP" mailing list shows as a seperate mailbox. But there is no way to pull just mails from that mailing list via API to replicate the functionality.

In Game

Out of Game

The Trash mailbox above is default on most clients, there is currently no way to access the Trash mailbox via API with labels.

 Labels:[{UnreadCount:0 LabelId:1 Name:Inbox Color:#ffffff} 
{UnreadCount:0 LabelId:2 Name:Sent Color:#ffffff} 
{UnreadCount:1 LabelId:4 Name:[Corp] Color:#ffffff}
 {UnreadCount:0 LabelId:8 Name:[Alliance] Color:#ffffff}]}```

@SpeedProg
Copy link

SpeedProg commented Jul 8, 2018

This feature is nice but wouldn't it make more sense to add an other parameter for this since it is no label? (or is it?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants