Received: by 10.42.33.9 with SMTP id g9mr19151108icd.25.1351556584000;
        Mon, 29 Oct 2012 17:23:04 -0700 (PDT)
X-BeenThere: 37signals-api@googlegroups.com
Received: by 10.50.41.132 with SMTP id f4ls7205006igl.1.gmail; Mon, 29 Oct
 2012 17:23:02 -0700 (PDT)
Received: by 10.42.89.193 with SMTP id h1mr17708429icm.31.1351556582830;
        Mon, 29 Oct 2012 17:23:02 -0700 (PDT)
Received: by 10.42.89.193 with SMTP id h1mr17708425icm.31.1351556582790;
        Mon, 29 Oct 2012 17:23:02 -0700 (PDT)
Return-Path: <j...@37signals.com>
Received: from mail-ia0-f171.google.com (mail-ia0-f171.google.com [209.85.210.171])
        by gmr-mx.google.com with ESMTPS id wu4si1176480igb.3.2012.10.29.17.23.02
        (version=TLSv1/SSLv3 cipher=OTHER);
        Mon, 29 Oct 2012 17:23:02 -0700 (PDT)
Received-SPF: pass (google.com: domain of j...@37signals.com designates 209.85.210.171 as permitted sender) client-ip=209.85.210.171;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of j...@37signals.com designates 209.85.210.171 as permitted sender) smtp.mail=j...@37signals.com; dkim=pass header...@37signals.com
Received: by mail-ia0-f171.google.com with SMTP id u21so4589225ial.2
        for <37signals-api@googlegroups.com>; Mon, 29 Oct 2012 17:23:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=37signals.com; s=gapps;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        bh=s2eskvnoIJ3N90igdru71viw0SOd+AY5buEelq9cq+U=;
        b=L9wLDiwwZypid8baQakOL1t3iXqLeEP85tQcvlNusDNXT9O5QcK5hL/JTVHyj3HdSs
         JRFo8lEx1x5WAN0uewgucujCpssPh95XXnXSoTkW7WGmuFaVtdQz3vlEPttvQyVtvJSG
         TE2H4iw7AJuieSQw5V9TWAvx1MH6+A+WkHAdY=
        d=google.com; s=20120113;
        h=content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer
         :x-gm-message-state;
        bh=s2eskvnoIJ3N90igdru71viw0SOd+AY5buEelq9cq+U=;
        b=AY64oVTz9Gvy0jkIUzIhsuSUcG2ccPnqiirpRx1w/k911M2wSThoJndC69J0qpm3/7
         KcbTzt+RgcfJ2/tzukHEm8PCaYeCM0B6l94G1aSveb/m48eJq7fsUFYiqttySmzFxDNy
         pizRUv0EcUq1CdSMRH9UgE92Xb07EQ6UbMvwIhfpxR30AA40XSdlavmKZiQbWa7VCVB2
         M4IoiCFqnaVTIP2JwIHKnoY/8Bcp3McEaXADqyA2skAbXGBxhgUAM6m24RhteB9uG9PX
         7MjtPCggbqyJaCbTzhxPyXOfZw9WuhkwPYubax5eOGa2W5fzu1QzthHJ0ZuK3CYqZ4Jd
         Xdmg==
Received: by 10.50.219.202 with SMTP id pq10mr11408771igc.18.1351556582478;
        Mon, 29 Oct 2012 17:23:02 -0700 (PDT)
Return-Path: <j...@37signals.com>
Received: from [10.0.1.101] (49-42-81.wireless.iaw.on.ca. [69.49.42.81])
        by mx.google.com with ESMTPS id v12sm7355761igv.3.2012.10.29.17.23.00
        (version=SSLv3 cipher=OTHER);
        Mon, 29 Oct 2012 17:23:01 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [37signals API] what's the best way to determine whether a user's superpowers basecamp?
From: Jeffrey Hardy <j...@37signals.com>
In-Reply-To: <10b4f321-898e-4b82-a5b4-1bdc16b61c77@googlegroups.com>
Date: Mon, 29 Oct 2012 20:22:58 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D4572382-712C-4FAA-889F-28417988D...@37signals.com>
References: <10b4f321-898e-4b82-a5b4-1bdc16b61c77@googlegroups.com>
To: 37signals-api@googlegroups.com
X-Mailer: Apple Mail (2.1499)
X-Gm-Message-State: ALoCoQm8q1EC69xZ1/YQfhoUPo2Mrr+umZt9k2iq+Ca9WMFTmYk6uM2b/BU+zXV4PUc758nuhUXP

Hi Boris --

On 2012-10-20, at 8:54 PM, Boris Jabes <bja...@gmail.com> wrote:
> I'm working through the Basecamp API and I was wondering whether there =
is a way to see that a user has admin rights. Is there a flag or a =
non-modifying API request that can determine whether they are?

We just added the `admin` attribute to people. See =
https://github.com/37signals/bcx-api/blob/master/sections/people.md for =
the updated JSON.

--
Jeffrey Hardy
http://37signals.com