Date   

Re: Interacting with groups using the group name instead of the identifier

 

On Mon, Oct 2, 2017 at 10:41 PM, Isaac Whitfield <iw@...> wrote:
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 on the API (since it should be unique?). Is there any intent to make this possible? If not, could we add a new API which will lookup the group identifier for a group name as a workaround?

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? 

Thanks,
Mark 


Re: Is it possible to remove a user from a group directly?

 

Hi Isaac,

On Mon, Oct 2, 2017 at 10:38 PM, Isaac Whitfield <iw@...> wrote:
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. 

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 


Interacting with groups using the group name instead of the identifier

Isaac Whitfield <iw@...>
 

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 on the API (since it should be unique?). Is there any intent to make this possible? If not, could we add a new API which will lookup the group identifier for a group name as a workaround?

Thanks in advance,
Isaac


Is it possible to remove a user from a group directly?

Isaac Whitfield <iw@...>
 

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


Re: Consider removing group_id as required for sub-group creation

Isaac Whitfield <iw@...>
 

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 slower!

Thank you for the quick response,
Isaac


Re: Consider removing group_id as required for sub-group creation

 

Hi Isaac,

On Fri, Sep 29, 2017 at 7:31 AM, Isaac Whitfield <iw@...> wrote:
Is it possible that this field requirement could be removed in favour of auto-incrementing identifiers? 

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 change that parameter name to parent_group_id?

Thanks,
Mark


Consider removing group_id as required for sub-group creation

Isaac Whitfield <iw@...>
 

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 that you need to store some sort of reference on the client side to avoid clashing identifiers in future creation.

Could this field become either auto-incrementing or a String type (e.g. UUID)? Either one removes the need to keep track of the identifier state in the clients.

Thanks,
Isaac


/downloadarchives

 

Hi All,

I've added a /downloadarchives endpoint.

Cheers,
Mark


Re: API for Message Metrics?

 

Hi Mark,

On Mon, Aug 28, 2017 at 9:53 AM, Mark Griffin <mgriffin@...> wrote:
Wonder if there will be, or could be, an an API to grab raw messages archives (ie, mbox).

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 API.

Thanks,
Mark 


API for Message Metrics?

Mark Griffin
 

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 have some "metric" focused APIs that could be used to render these visualizations. For example, here is a pretty slick visualization based on historical activity https://opnfv.biterg.io/app/kibana#/dashboard/MailingLists


/updatesub and /deletesub

 

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 functionality some more.

Most of the management functions are now implemented. I'm going to take a week and work on some other things and then I'll get back to the API again. Please let me know if you have any questions/suggestions.

Thanks,
Mark


Re: Create subgroup issues

 

Hi James,

On Sun, Aug 20, 2017 at 4:29 AM, James Milligan <james@...> wrote:
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 with both query params or a body net the same result.

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 


Create subgroup issues

James Milligan
 

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 with both query params or a body net the same result.

--
Kind regards,

James Milligan
Need to integrate with the Groups.io API in Java? Check out the Groups.io API Java client


Re: Friday updates

James Milligan
 

Thanks Mark. I guess it depends - bad request feels more like there's a field or otherwise structural issue with the request, whereas invalid value is (to me) saying that the request itself is valid, but what you're trying to set is wrong. If you had to choose one I'd stick with bad request though.
--
Kind regards,

James Milligan
Need to integrate with the Groups.io API in Java? Check out the Groups.io API Java client


Re: Updates

James Milligan
 

Yep, working for me too. Cheers!
--
Kind regards,

James Milligan
Need to integrate with the Groups.io API in Java? Check out the Groups.io API Java client


Friday updates

 

Hi All,

There is now a working changelog/diff function for the API docs. It's at 


It's not perfect, but should hopefully be helpful.

I've also changed the URL for the API docs; it's now at https://groups.io/api

The /createsubgroup endpoint is now working and the docs have been updated with the correct parameters.

I noticed today that I'm a bit inconsistent in using "bad_request" versus "invalid_value" in errors. My gut says to get rid of one of them. I will figure that out early next week.

Please let me know if you see anything or have suggestions. 

Thanks,
Mark


Re: Updates

 

On Fri, Aug 18, 2017 at 9:33 AM, James Milligan <james@...> wrote:
On Thu, Aug 17, 2017 at 04:08 pm, Mark Fletcher wrote:
Please try it now. I've also updated it to take some additional parameters.
Hmm, still getting 200 OK but the object hasn't changed :-/

Ok, I think it's fixed now for sure.

Thanks,
Mark 


Re: Updates

James Milligan
 

On Thu, Aug 17, 2017 at 04:08 pm, Mark Fletcher wrote:
Please try it now. I've also updated it to take some additional parameters.
Hmm, still getting 200 OK but the object hasn't changed :-/
 
It would be really nice (rather, simpler for me!) if the API accepted JSON on the way in as well as for the response.
Understood. For at least the time being, I need to keep the calls as they are. I'm doing the API this way because I can repurpose the existing web code, with not a lot of change, to also run the api server, and I can have both servers share the same code. A lot less development risk, and I'm able to get more done quickly. Plus it's how Stripe's API works, and I try to copy them whenever I can because I think their API is very well thought out. :)
No worries - #wishlist for the future then!
I hope tomorrow to have a system in place where you can easily diff different versions of the API docs, so you can see what's changed.
Smashing - that'll really help.
 
--
Kind regards,

James Milligan
Need to integrate with the Groups.io API in Java? Check out the Groups.io API Java client


Re: Updates

 

Hi James,

On Thu, Aug 17, 2017 at 11:15 AM, James Milligan <james@...> wrote:
Hi Mark,

The /updateuser endpoint seems to accept (200 OK) my requests, but doesn't actually proceed to update the user:

Please try it now. I've also updated it to take some additional parameters.

Error objects now have an "object" field, to be consistent with the other objects. I also changed user_status_notconfirmed to user_status_not_confirmed, to be more consistent.

 
It would be really nice (rather, simpler for me!) if the API accepted JSON on the way in as well as for the response.

Understood. For at least the time being, I need to keep the calls as they are. I'm doing the API this way because I can repurpose the existing web code, with not a lot of change, to also run the api server, and I can have both servers share the same code. A lot less development risk, and I'm able to get more done quickly. Plus it's how Stripe's API works, and I try to copy them whenever I can because I think their API is very well thought out. :)

I hope tomorrow to have a system in place where you can easily diff different versions of the API docs, so you can see what's changed.


Thanks,
Mark


Re: Updates

James Milligan
 

Hi Mark,

The /updateuser endpoint seems to accept (200 OK) my requests, but doesn't actually proceed to update the user:

curl -X POST \
  https://api.groups.io/v1/updateuser \
  -H 'authorization: Basic ...' \
  -H 'cache-control: no-cache' \
  -d time_pref=time_absolute
It just returns the existing user as it was beforehand. I did try with a password=1 request to see whether it would return password_too_short but no luck :(

It would be really nice (rather, simpler for me!) if the API accepted JSON on the way in as well as for the response.

--
Kind regards,

James Milligan
Need to integrate with the Groups.io API in Java? Check out the Groups.io API Java client

221 - 240 of 253