Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org Received: (qmail 16114 invoked from network); 13 Jun 2010 08:13:09 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 13 Jun 2010 08:13:09 -0000 Received: (qmail 57105 invoked by uid 500); 13 Jun 2010 08:13:09 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 57049 invoked by uid 500); 13 Jun 2010 08:13:07 -0000 Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: esme-dev@incubator.apache.org Delivered-To: mailing list esme-dev@incubator.apache.org Received: (qmail 57041 invoked by uid 99); 13 Jun 2010 08:13:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 13 Jun 2010 08:13:06 +0000 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=AWL,FREEMAIL_FROM,HTML_MESSAGE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of hirsch.dick@gmail.com designates 209.85.161.47 as permitted sender) Received: from [209.85.161.47] (HELO mail-fx0-f47.google.com) (209.85.161.47) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 13 Jun 2010 08:13:01 +0000 Received: by fxm9 with SMTP id 9so1959701fxm.6 for ; Sun, 13 Jun 2010 01:12:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=2a6tdQLMIEhcjpPA4/KWiXvUTeaMjyqr+ne7007HNI8=; b=V4cv+AfPxRR7Ns3qoHEFcmgmJ9Dx2JDPlZb+9GvVytHJTNqzXMrPJSucDPJmflayOO AyUDhcJRYa4FIdaFot02AH3Ixivb8Q08zDyWpDJtHr0SX0u7JqeUtJSUna1mk8Y7Z2Z5 qYWjkvwwg56C4I7DQwu0TlR3VKmB82GvFzsFQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=ArRmngUJfe1FS+DN/vMU5yJ+QXJX2OcM1IlLWzQOqppKg4osiANpVuCnQ07q6szmeD 4mpQZ6y0RcfePjGtCtQoByBktabifIZoz4UHmsQ2MP0TRcgYC3UJah0Tj34YOC5yv7VW g1Ol8OoVXZDfzdoijSVQGuk3mwhmW6HN/1tQc= MIME-Version: 1.0 Received: by 10.103.79.7 with SMTP id g7mr1182481mul.51.1276416760135; Sun, 13 Jun 2010 01:12:40 -0700 (PDT) Received: by 10.103.239.5 with HTTP; Sun, 13 Jun 2010 01:12:40 -0700 (PDT) In-Reply-To: References: Date: Sun, 13 Jun 2010 10:12:40 +0200 Message-ID: Subject: Re: I've signed up for APIGee for ESME From: Richard Hirsch To: esme-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=0016e65c7d6a92c2840488e4ef93 --0016e65c7d6a92c2840488e4ef93 Content-Type: text/plain; charset=ISO-8859-1 Right now, our twitter api is out of synch with the official Twitter api - we are working right now to update it. On Fri, Jun 11, 2010 at 12:19 PM, Richard Hirsch wrote: > to use it you have to do something like this: > > curl --dump-header headers -d "token=31FGZ0R0M15NTD2LSOS0BKC5Y0P5JOVAC" > http://api2.esme.apigee.com/api2/session > > Don't worry - token is a fake one. > > D. > > On Fri, Jun 11, 2010 at 10:42 AM, Richard Hirsch wrote: > >> APIGee allows you to monitor and test api usage. I've signed up and the >> api2 api is available with api2.esme.apigee.co. >> >> I'll do the twitter api next. The advantage with using apigee for this api >> is that we can see exactly how various twitter clients are using ESME and >> what sort of problems they are having. I'll keep you abreast on what I >> learn. This api is available with this URL: twitter.esme.apigee.com. >> Please use this when connecting with any client (Tweetdeck, etc.) >> >> Have fun. >> >> D. >> >> > --0016e65c7d6a92c2840488e4ef93--