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

Is there a way to pull the heather data into my app? #421

Closed
ghost opened this issue Nov 30, 2017 · 7 comments
Closed

Is there a way to pull the heather data into my app? #421

ghost opened this issue Nov 30, 2017 · 7 comments

Comments

@ghost
Copy link

ghost commented Nov 30, 2017

Hi I would like to know if I can pull this data into my app, and trying to decide if it even makes sense to do so.

postal heather

I understand I can calculate all these results locally by using webhooks and counting messages, but since postal is already doing all this work, would it make sense to pull the data from postal? And if it does, How can I do that?

@ghost
Copy link
Author

ghost commented Nov 30, 2017

Then in the screenshots posted in the wiki I can see "Sending via shared IP Pool" Is that something I can get via API or webhook?

BTW, this piece of information is not showing on my own install, is that due to my configuration or has it been removed lately?

@willpower232
Copy link
Collaborator

There isn't a statistics API so unfortunately this information is not available outside of Postal.

Nothing is displayed in that spot unless you are sending from an IP Pool. If you would like to send from multiple IP addresses then have a look here.

@ghost
Copy link
Author

ghost commented Nov 30, 2017

Thank you @willpower232, do you think it makes sense to make this a feature request or since it can be calculated locally it´s utterly unnecessary or useless?

@willpower232
Copy link
Collaborator

There is a wider issue about the lack of general information from Postal. IMHO it would always be better to get the stats from the source rather than calculate it yourself.

@ghost
Copy link
Author

ghost commented Nov 30, 2017

Agreed, should I close this issue and open a new one for feature request or it´s better to keep it all in one place?

@willpower232
Copy link
Collaborator

Better to leave this one open I would have said

@adamcooke
Copy link
Contributor

I've made a new enhancement issue for this #453

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

No branches or pull requests

2 participants