Get Meetup Id when authorized

[Corey Giordana]

Hello and thank you for the help in advance,

I am working on a Meetup "integration" and I am nearing the end.  I have a website that is grabbing all members, events, and rsvps from meetup and automatically creating them in the 2nd website.  New members, events, and rsvps are found throughout the day and properly added to the new site.  The problem I am running into is that people who find the new site directly (no meetup account) are able to create an account directly on the new site (this is fine and expected).  Then they realize lots of people talking about meetup and go there to create an account as well.  Then the website will do what it is supposed to do and create a new account for that member on meetup since it will find them as a new meetup member.  Now this particular user has two different accounts on the new website.  It's unknown which account they will log into on the new site now (most likely the original account), but I am looking for a way for the new site to inform me or somehow notice the issue and properly combine the accounts.  The only thing I have come up with so far is to do something when a user authorizes the new website access to their meetup account via oauth.  Somehow I will need to echo the user id of the visitor on the new site along with the meetup id they just authorized where I could then check the database using those two pieces.  If the user on the new website has no meetup id in that field of the db table but authorized a meetup id, that would mean there are two separate accounts for that one user.  I don't think I can find the problem the first time the new website finds a new user on meetup simply because there is no info I get from meetup to  define this?  I don't get email addresses so their does not seem to be any concrete data I can use at that time.  If somebody has a different idea than checking when oauth is used I am open to suggestions.  If this is my only option I guess my question would be can I somehow get a meetup id or some type of information from meetup at the time a visitor uses my oauth setup and grants access to the new website?  I would think I would be able grap the user id in the new website and store it, but I need something from meetup to cross reference that with.  The new website is a Joomla website in case that information is needed.  I apologize so much for the long message and would like to thank you in advance for any insight on the situation. :)

- Corey

This e-mail and any attachments is intended for the use and/or authorized (by WebCitz, LLC) distribution of the individual or entity to which this email is addressed. This email may contain information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you have not been specifically authorized by WebCitz, LLC to distribute you are legally prohibited from distributing or otherwise disclosing this information in any manner outside your entity. If you are not the intended recipient and have received this in error, please inform us promptly by reply email. Then please delete this email and destroy any printed copy. Please be advised that if you are not the intended recipient, you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Thank you in advance for your cooperation.

[Mike Fulton]

Long messages aren't a problem, but long, wide paragraphs are hard to read. Break it up a bit.

The simple answer is you can't get there from here.  Without the user's input, there is no information you can get about a user from Meetup that will absolutely identify them as being the same person that also signed up for an account on your website. The only way to do it is for the user to initiate the association between the two sites.

I don't think it's a good idea to automatically create accounts for Meetup users that haven't actually visited your site yet.  It seems to serve no useful purpose.  If you want to track and display activity from Meetup on your site, that's really a different problem from local user authentication.  Furthermore, some people will see it as a privacy breech if you're associating their identities across sites without permission.

I think what you really want to do is have users create their accounts on your site, and then have a "login with Meetup" button which would do the Oauth authentication and then once that's approved by the user, you can request the user's Meetup info.  This will include their Meetup member ID, which you can then store with your website's own user record.

Mike

[Nathan Hamblen]

On Sun, May 11, 2014 at 5:37 PM, Mike Fulton <mikeful...@gmail.com> wrote:

I think what you really want to do is have users create their accounts on your site, and then have a "login with Meetup" button which would do the Oauth authentication and then once that's approved by the user, you can request the user's Meetup info.  This will include their Meetup member ID, which you can then store with your website's own user record.

This is on the right track. The Meetup OAuth supports registration, so if Corey sends users to Meetup as part of his site's registration process they can either log in or sign up at that point. They will be redirected back to the third party site after they are authenticated with Meetup.

Nathan

[Corey Giordana]

Thank you Gentlemen for the help on this and I apologize that I did not send my reply.  I did see your responses and the days kept getting past me (been a regular thing lately).  I agree with everything you are saying, but am running into some troubles due to what the customer is requesting.

I have one more question:

Is there a way for me to check what meetup users of a specific meetup group have granted access to my / my customer's third party website?

Again, I really appreciate all your insight and help.

- Corey

[Doug Tangren]

On Sun, May 18, 2014 at 9:54 PM, Corey Giordana <co...@webcitz.com> wrote:

Thank you Gentlemen for the help on this and I apologize that I did not send my reply.  I did see your responses and the days kept getting past me (been a regular thing lately).  I agree with everything you are saying, but am running into some troubles due to what the customer is requesting.

I have one more question:

Is there a way for me to check what meetup users of a specific meetup group have granted access to my / my customer's third party website?

Again, I really appreciate all your insight and help.

There's a few ways to go about doing this. 

When a user grants access to your site, a set of credentials are returned to your server in the form of oauth tokens. You are welcome to store these on your servers as the are represent temporal authorization for you to access the Meetup API on their behalf. At the time of receiving the token you can make a followup call to GET /2/member/self ( http://www.meetup.com/meetup_api/docs/2/member/#get ) to grab the authorized member's member id and store that along side the authorized oauth credentials. 

If you then want to check which authorized user's are a members of a target group, you could use the GET /2/profiles API filtering by a group_id or group_urlname in question with a comma delimited list of member_ids, something like http://www.meetup.com/meetup_api/console/?path=/2/profiles&group_urlname=meetup-api-testing&member_id=1,2,3 for example. Just inspect the results field in the response for presence of member's owning the target member_ids.

If you just have a oauth authorized credentials and not a member id on hand, you can query the either of the profiles APIs with the member_id of "self". "self" represents an alias for the currently authorized member's id across all API methods.

Here is an example of querying for a member of a group ( the group id and member id are path params ) in the GET /2/profile/:gid/:mid API. 

http://www.meetup.com/meetup_api/console/?path=%2F2%2Fprofile%2F%3Agid%2F%3Amid&:gid=1556336&:mid=self

 

This will return a 404 if the authorized member is not an authorized member of the group.

- Corey

On Saturday, May 10, 2014 3:13:12 PM UTC-5, Corey Giordana wrote:

Hello and thank you for the help in advance,

I am working on a Meetup "integration" and I am nearing the end.  I have a website that is grabbing all members, events, and rsvps from meetup and automatically creating them in the 2nd website.  New members, events, and rsvps are found throughout the day and properly added to the new site.  The problem I am running into is that people who find the new site directly (no meetup account) are able to create an account directly on the new site (this is fine and expected).  Then they realize lots of people talking about meetup and go there to create an account as well.  Then the website will do what it is supposed to do and create a new account for that member on meetup since it will find them as a new meetup member.  Now this particular user has two different accounts on the new website.  It's unknown which account they will log into on the new site now (most likely the original account), but I am looking for a way for the new site to inform me or somehow notice the issue and properly combine the accounts.  The only thing I have come up with so far is to do something when a user authorizes the new website access to their meetup account via oauth.  Somehow I will need to echo the user id of the visitor on the new site along with the meetup id they just authorized where I could then check the database using those two pieces.  If the user on the new website has no meetup id in that field of the db table but authorized a meetup id, that would mean there are two separate accounts for that one user.  I don't think I can find the problem the first time the new website finds a new user on meetup simply because there is no info I get from meetup to  define this?  I don't get email addresses so their does not seem to be any concrete data I can use at that time.  If somebody has a different idea than checking when oauth is used I am open to suggestions.  If this is my only option I guess my question would be can I somehow get a meetup id or some type of information from meetup at the time a visitor uses my oauth setup and grants access to the new website?  I would think I would be able grap the user id in the new website and store it, but I need something from meetup to cross reference that with.  The new website is a Joomla website in case that information is needed.  I apologize so much for the long message and would like to thank you in advance for any insight on the situation. :)

- Corey

This e-mail and any attachments is intended for the use and/or authorized (by WebCitz, LLC) distribution of the individual or entity to which this email is addressed. This email may contain information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you have not been specifically authorized by WebCitz, LLC to distribute you are legally prohibited from distributing or otherwise disclosing this information in any manner outside your entity. If you are not the intended recipient and have received this in error, please inform us promptly by reply email. Then please delete this email and destroy any printed copy. Please be advised that if you are not the intended recipient, you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Thank you in advance for your cooperation.

This e-mail and any attachments is intended for the use and/or authorized (by WebCitz, LLC) distribution of the individual or entity to which this email is addressed. This email may contain information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you have not been specifically authorized by WebCitz, LLC to distribute you are legally prohibited from distributing or otherwise disclosing this information in any manner outside your entity. If you are not the intended recipient and have received this in error, please inform us promptly by reply email. Then please delete this email and destroy any printed copy. Please be advised that if you are not the intended recipient, you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Thank you in advance for your cooperation.

--
--
You received this message because you are subscribed to the Google
Groups "Meetup API" group.
To unsubscribe from this group, send email to
meetup-api+...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/meetup-api?hl=en?hl=en

---
You received this message because you are subscribed to the Google Groups "Meetup API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meetup-api+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Corey Giordana]

Hello Doug,

First I have to apologize for the long delay again...I do not know where time / days go lately.  Shortly after my last post I learned of the "self" feature you mentioned.  I tested it out along with the info you provided and that does exactly what I needed for some initial log in pieces.

I thought of one other issue I see happening and I would be curious on your input.

I believe the new website that has been created will be found by several visitors via standard Google / Yahoo /  Bing searches.  They will create an account on the website and will begin communicating with other members.  They will learn that many people of the website also seem to have accounts on Meetup where they talk as well.  The new member will then create an account directly on Meetup vs the option on the new site to do this since everybody else seems to have an account with Meetup.  The new website will then do what it has been designed to do which is find a new member on meetup and create an automated account for this member resulting in two accounts on the new website for this particular member (original account they created & the automated account the new website creates when finding a new meetup member).

The problem this creates is that if this member now rsvps for an event the new website will show a profile for the automated account that was created for this member since it's the account that will have a Meetup Id associated to it (via backend id).  This user most likely will not be using that account (I think they will log into the original) which will display the automated profile and not the profile the user specifically created them self.

I can fix this problem if I can somehow have the new website automatically check if a logged in user has authenticated with Meetup then check the database to see if the specific user id also has the meetup id of that user in the specific table in the database (i am so sorry for that statement).  If the meetup id is not there I know I have a problem and that user should in fact have two accounts where I need to merge them together.

I would like to be able to automate that somehow, and I am burning my brain thinking about options. 

I hope this was not too confusing and I would really be interested in your thoughts on this.  Sorry again for all the troubles, but I really appreciate the time you take to help others :)

- Corey

On Saturday, May 10, 2014 3:13:12 PM UTC-5, Corey Giordana wrote:

[Doug Tangren]

On Wed, May 21, 2014 at 9:36 PM, Corey Giordana <co...@webcitz.com> wrote:

Hello Doug,

First I have to apologize for the long delay again...I do not know where time / days go lately.  Shortly after my last post I learned of the "self" feature you mentioned.  I tested it out along with the info you provided and that does exactly what I needed for some initial log in pieces.

I thought of one other issue I see happening and I would be curious on your input.

I believe the new website that has been created will be found by several visitors via standard Google / Yahoo /  Bing searches.  They will create an account on the website and will begin communicating with other members.  They will learn that many people of the website also seem to have accounts on Meetup where they talk as well.  The new member will then create an account directly on Meetup vs the option on the new site to do this since everybody else seems to have an account with Meetup.  The new website will then do what it has been designed to do which is find a new member on meetup and create an automated account for this member

When you say "find a new member on Meetup", is this referring to looking up the Meetup Member using Meetup API credentials and finding the member referenced by self?

 

resulting in two accounts on the new website for this particular member (original account they created & the automated account the new website creates when finding a new Meetup member).

If you are asking existing users of your site to tie their accounts on your site to Meetup, when the OAuth authorize flow redirects back to your application, you can check for the currently logged in member and do the binding/merging at this time.

 

The problem this creates is that if this member now RSVPs for an event the new website will show a profile for the automated account that was created for this member since it's the account that will have a Meetup Id associated to it (via backend id).  

This seems like a confusing user experience. I don't think you would ever want to auto-generate and account before checking to see if there's an authenticated session which you can bind the Meetup member info to. This would help avoid some of that confusion.

 

This user most likely will not be using that account (I think they will log into the original) which will display the automated profile and not the profile the user specifically created them self.

I can fix this problem if I can somehow have the new website automatically check if a logged in user has authenticated with Meetup then check the database to see if the specific user id also has the Meetup id of that user in the specific table in the database (i am so sorry for that statement).  If the Meetup id is not there I know I have a problem and that user should in fact have two accounts where I need to merge them together.

The member will always be present when asking to grant access to their information on meetup.com. When navigating into this flow from your site they would be in one of two states

1) not logged in initially on your site, in which case, when the user is redirected back to your site you can stub out the specifics you need to generate an account for your site when the Meetup member's information

3) logged in initially on your site, in which case you would be asking them to tie their account on your site with their account on Meetup. After being redirected back to your site from Meetups OAuth flow you could do that binding then

 

I would like to be able to automate that somehow, and I am burning my brain thinking about options. 

I hope this was not too confusing and I would really be interested in your thoughts on this.  Sorry again for all the troubles, but I really appreciate the time you take to help others :)

- Corey

On Saturday, May 10, 2014 3:13:12 PM UTC-5, Corey Giordana wrote:

Hello and thank you for the help in advance,

I am working on a Meetup "integration" and I am nearing the end.  I have a website that is grabbing all members, events, and rsvps from meetup and automatically creating them in the 2nd website.  New members, events, and rsvps are found throughout the day and properly added to the new site.  The problem I am running into is that people who find the new site directly (no meetup account) are able to create an account directly on the new site (this is fine and expected).  Then they realize lots of people talking about meetup and go there to create an account as well.  Then the website will do what it is supposed to do and create a new account for that member on meetup since it will find them as a new meetup member.  Now this particular user has two different accounts on the new website.  It's unknown which account they will log into on the new site now (most likely the original account), but I am looking for a way for the new site to inform me or somehow notice the issue and properly combine the accounts.  The only thing I have come up with so far is to do something when a user authorizes the new website access to their meetup account via oauth.  Somehow I will need to echo the user id of the visitor on the new site along with the meetup id they just authorized where I could then check the database using those two pieces.  If the user on the new website has no meetup id in that field of the db table but authorized a meetup id, that would mean there are two separate accounts for that one user.  I don't think I can find the problem the first time the new website finds a new user on meetup simply because there is no info I get from meetup to  define this?  I don't get email addresses so their does not seem to be any concrete data I can use at that time.  If somebody has a different idea than checking when oauth is used I am open to suggestions.  If this is my only option I guess my question would be can I somehow get a meetup id or some type of information from meetup at the time a visitor uses my oauth setup and grants access to the new website?  I would think I would be able grap the user id in the new website and store it, but I need something from meetup to cross reference that with.  The new website is a Joomla website in case that information is needed.  I apologize so much for the long message and would like to thank you in advance for any insight on the situation. :)

- Corey

This e-mail and any attachments is intended for the use and/or authorized (by WebCitz, LLC) distribution of the individual or entity to which this email is addressed. This email may contain information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you have not been specifically authorized by WebCitz, LLC to distribute you are legally prohibited from distributing or otherwise disclosing this information in any manner outside your entity. If you are not the intended recipient and have received this in error, please inform us promptly by reply email. Then please delete this email and destroy any printed copy. Please be advised that if you are not the intended recipient, you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Thank you in advance for your cooperation.

This e-mail and any attachments is intended for the use and/or authorized (by WebCitz, LLC) distribution of the individual or entity to which this email is addressed. This email may contain information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you have not been specifically authorized by WebCitz, LLC to distribute you are legally prohibited from distributing or otherwise disclosing this information in any manner outside your entity. If you are not the intended recipient and have received this in error, please inform us promptly by reply email. Then please delete this email and destroy any printed copy. Please be advised that if you are not the intended recipient, you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Thank you in advance for your cooperation.

--

[Corey Giordana]

Hello Doug,

I agree with everything you are mentioning and will provide feedback on your question below:

Your Question: When you say "find a new member on Meetup", is this referring to looking up the Meetup Member using Meetup API credentials and finding the member referenced by self?

The new website has not launched yet, but the customer requested I setup a piece to get member information for each member in his meetup group currently.  He wanted me to have an account created from this information on his site for each member in his meetup group (these members have never accessed their accounts on the new site yet).  When the site launches he will have informed each member that they already have an account on his new site and they will be able to request username and password credentials the first time they visit the new site.  Post launch the new site will check for new members multiple times a day that have joined his meetup group on meetup and create automatic accounts for them as well the same way the accounts were created prior to launch.

The reason he is having the accounts created automatically versus having the members create them if they want is due to a full events and calendar section on the new site.  He wants people to be able to view profiles of members attending events and the new site would show inaccurate information if rsvp'd members did not create an account on the new site yet.  The new website also has an emergency contact section that requires an account at least be created for each member to run properly.  He also does not want the new site to be dependent on Meetup for providing information since he would like to move towards the group being run completely on the new site in the long run.

The fact the new site automatically creates accounts for members is why I will run into some problems with duplicate accounts (I did express this to the customer, but he wants it to create them automatically).  I could setup a piece where I ask visitors to click a button to check for proper account "integration" where I could grab the user Id and meetup id and make sure they are listed together in the database, but I wish I could do this automatically in some way.

When you have a moment please let me know if I explained this in a good way or if this was extremely confusing.

Thank you again fine sir.

- Corey

On Saturday, May 10, 2014 3:13:12 PM UTC-5, Corey Giordana wrote:

[Doug Tangren]

On Thu, May 22, 2014 at 12:02 PM, Corey Giordana <co...@webcitz.com> wrote:

Hello Doug,

I agree with everything you are mentioning and will provide feedback on your question below:

Your Question: When you say "find a new member on Meetup", is this referring to looking up the Meetup Member using Meetup API credentials and finding the member referenced by self?

The new website has not launched yet, but the customer requested I setup a piece to get member information for each member in his meetup group currently.  He wanted me to have an account created from this information on his site for each member in his meetup group (these members have never accessed their accounts on the new site yet).

I would argue against this type of Meetup API usage. This will create confusion on the behalf of our member's when they find out their likeness has been used to create an account on a website they may have never visited.  I would say do not create an account using Meetup member data unless the Meetup member has explicitly opted to do so.

 

 When the site launches he will have informed each member that they already have an account on his new site and they will be able to request username and password credentials the first time they visit the new site.

 Post launch the new site will check for new members multiple times a day that have joined his meetup group on meetup and create automatic accounts for them as well the same way the accounts were created prior to launch.

Our member's may find this use of their member data creepy. I was not recommend copying their likeness into an account on a site they may have never visited.

 

The reason he is having the accounts created automatically versus having the members create them if they want is due to a full events and calendar section on the new site.  He wants people to be able to view profiles of members attending events and the new site would show inaccurate information if rsvp'd members did not create an account on the new site yet.

You could also just show a list of the members registered on your site along with the number of Meetup members not yet registered on your site.

 

 The new website also has an emergency contact section that requires an account at least be created for each member to run properly.

I'm not sure you will be able to contact a Meetup member that has not yet registered an account on your site. You would only be able to contact them after asking explicitly for some contact information when signing up for your site.

 

 He also does not want the new site to be dependent on Meetup for providing information since he would like to move towards the group being run completely on the new site in the long run.

This is starting to sound like you are phishing for members to pull them away from Meetup. This is not a usecase we want to facilitate on our platform. Can I ask what kind of website you are building?

 

The fact the new site automatically creates accounts for members is why I will run into some problems with duplicate accounts (I did express this to the customer, but he wants it to create them automatically).  I could setup a piece where I ask visitors to click a button to check for proper account "integration" where I could grab the user Id and meetup id and make sure they are listed together in the database, but I wish I could do this automatically in some way.

After reviewing this, in addition to the things I've mentioned above, I don't think auto creating accounts for member's, especially member's that have never visited your site, is a good idea in general.

 

When you have a moment please let me know if I explained this in a good way or if this was extremely confusing.

Thank you again fine sir.

- Corey

On Saturday, May 10, 2014 3:13:12 PM UTC-5, Corey Giordana wrote:

Hello and thank you for the help in advance,

I am working on a Meetup "integration" and I am nearing the end.  I have a website that is grabbing all members, events, and rsvps from meetup and automatically creating them in the 2nd website.  New members, events, and rsvps are found throughout the day and properly added to the new site.  The problem I am running into is that people who find the new site directly (no meetup account) are able to create an account directly on the new site (this is fine and expected).  Then they realize lots of people talking about meetup and go there to create an account as well.  Then the website will do what it is supposed to do and create a new account for that member on meetup since it will find them as a new meetup member.  Now this particular user has two different accounts on the new website.  It's unknown which account they will log into on the new site now (most likely the original account), but I am looking for a way for the new site to inform me or somehow notice the issue and properly combine the accounts.  The only thing I have come up with so far is to do something when a user authorizes the new website access to their meetup account via oauth.  Somehow I will need to echo the user id of the visitor on the new site along with the meetup id they just authorized where I could then check the database using those two pieces.  If the user on the new website has no meetup id in that field of the db table but authorized a meetup id, that would mean there are two separate accounts for that one user.  I don't think I can find the problem the first time the new website finds a new user on meetup simply because there is no info I get from meetup to  define this?  I don't get email addresses so their does not seem to be any concrete data I can use at that time.  If somebody has a different idea than checking when oauth is used I am open to suggestions.  If this is my only option I guess my question would be can I somehow get a meetup id or some type of information from meetup at the time a visitor uses my oauth setup and grants access to the new website?  I would think I would be able grap the user id in the new website and store it, but I need something from meetup to cross reference that with.  The new website is a Joomla website in case that information is needed.  I apologize so much for the long message and would like to thank you in advance for any insight on the situation. :)

- Corey

This e-mail and any attachments is intended for the use and/or authorized (by WebCitz, LLC) distribution of the individual or entity to which this email is addressed. This email may contain information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you have not been specifically authorized by WebCitz, LLC to distribute you are legally prohibited from distributing or otherwise disclosing this information in any manner outside your entity. If you are not the intended recipient and have received this in error, please inform us promptly by reply email. Then please delete this email and destroy any printed copy. Please be advised that if you are not the intended recipient, you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Thank you in advance for your cooperation.

This e-mail and any attachments is intended for the use and/or authorized (by WebCitz, LLC) distribution of the individual or entity to which this email is addressed. This email may contain information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you have not been specifically authorized by WebCitz, LLC to distribute you are legally prohibited from distributing or otherwise disclosing this information in any manner outside your entity. If you are not the intended recipient and have received this in error, please inform us promptly by reply email. Then please delete this email and destroy any printed copy. Please be advised that if you are not the intended recipient, you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Thank you in advance for your cooperation.

--

[Corey Giordana]

Hello Doug,

I hope everything is going well and again I really appreciate all your input you have provided. I give you my word that this is not any form of a phishing setup.  It is a legitimate group that gets together every week (multiple times) and the group creator is simply having this website created to provide his members additional, completely optional, offerings.  The main reason for the website creation is an emergency contact section that is fully optional, but provides a way for members to securely provide emergency contact details should something happen during an event originated on Meetup or the new website.  The feature is hoped to not be needed, but given the area of interest all the members share it is a possibility (Ex: Hiking).

Thanks again so much Doug.

On Saturday, May 10, 2014 3:13:12 PM UTC-5, Corey Giordana wrote:

[I Burch]

Does anyone know a easy way to get the group ID for meetups you are the organizer.  I am trying to get the API to work.

Thanks

[Doug Tangren]

On Fri, Jun 6, 2014 at 8:12 AM, I Burch <eventpo...@gmail.com> wrote:

Does anyone know a easy way to get the group ID for meetups you are the organizer.  I am trying to get the API to work.

Try 2/groups with organizer_id = your member id

http://www.meetup.com/meetup_api/console/?path=%2F2%2Fgroups&organizer_id=YOUR_MEMBER_ID

 

This should return all the meetup groups you are an organizer in.

Typically, most cases where a member_id is expected allows you to substitute the literal member id with the "self" alias. organizer_id doesn't support that but I can make that change.

--