The createsubgroup endpoint doesn't seem to like my requests, I receive bad_request on sub_group_name. The docs don't make it particularly clear whether it should be a GET or POST, but trying either

Hi James, I think it should be working now. I've also fixed up the docs a bit about it. Also, I've added a working /deletegroup endpoint, and improved how the diff'ed docs look. Thanks, Mark

Hi, /updatesub and /deletesub now work. Also, I've gone through and fixed some inconsistencies in the documentation (formatting, how it's laid out, etc). Finally, I've improved the API doc diff

Wonder if there will be, or could be, an an API to grab raw messages archives (ie, mbox). This would be used to render some dashboard visualizations of historical activity. Maybe better, would be to

Hi Mark, Yep, there definitely will be. You can already download archives from the website, in mbox format. Adding an API will be simple and I'll get to that next week when I'm back working on the

Hi All, I've added a /downloadarchives endpoint. Cheers, Mark

Is it possible that this field requirement could be removed in favour of auto-incrementing identifiers? The combination of having to provide the identifier, along with the type being numeric, means

Hi Isaac, Sorry for the confusion. The group_id parameter on /createsubgroup refers to the ID of the parent group of your to-be-created sub group, not the sub group you are creating. Perhaps I should

Hi Mark, Actually, re-reading the documentation this makes perfect sense and is even pointed out. Not entirely sure how I missed it. I think the existing parameter name is fine and I just need to read

I'm wondering if there's some way to remove a user from a group directly, without the subscription identifier? I'm thinking something similar to "direct add" but in reverse. Thanks, Isaac

In our use case, users will interact with groups directly using the group name - we don't want to store a group identifier mapped to each group name, so it would be nice if we could use the group name

Hi Isaac, Currently premium groups have a bulk remove feature. I will convert that into an API call. It will take one or more email addresses. Should be done by the end of the week. Thanks, Mark

Hmm, yes that does seem to be a missing bit. I will modify the /getgroup endpoint to take either a group_id or a group_name. For adding that to all calls, what do you anticipate your work flow to be?

Hi All, There's a new /bulkremovemembers API endpoint, to remove one or more members by email address. Also, /getgroup can take a group_name parameter in the place of a group_id parameter. Please let

I went ahead and added the group_name parameter to all API endpoints. So now, any endpoint that requires a group specification can take either a group_id or a group_name. Thanks,Mark

Hi All, I've added a new endpoint, /creategroup, to create a new group. In addition, I've added some options to /createsubgroup to determine what kind of subscription is automatically generated for

Hi Mark, I've been trying out the new /creategroup API but I get an error back with the code "group_not_found"; any ideas if I'm doing something wrong? Thanks, IW

Hi Isaac, Sorry about that bug. It should be fixed now. Thanks, Mark

Hey Mark, Yep, got past that error. Unfortunately now seeing "bad_request" and the extra just says "privacy". I tried setting "group_privacy_none" and "group_privacy_unlisted". Any idea what I might

HI Isaac, Looks like you were submitted GET requests. That endpoint (and any endpoint that modifies things) requires a POST. I will look into adding a custom error message for that. Also, it appears