Business Mashups Best of the Web APIs

Business Mashups: Best of the Web APIs Ron Hess, salesforce.com Jon Jessup, Infopia Charlie Wood, Spanning Partners Track: New AppExchange Developer

Safe Harbor Statement

“ Safe harbor” statement under the Private Securities Litigation Reform Act of 1995: This presentation may contain forward-looking statements the achievement of which involves risks, uncertainties and assumptions. If any such risks or uncertainties materialize or if any of the assumptions proves incorrect, our results could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services.

The risks and uncertainties referred to above include - but are not limited to - risks associated with the integration of Sendia Corporation’s technology, operations, infrastructure and personnel with ours; unexpected costs or delays incurred in integrating Sendia with salesforce.com, which could adversely affect our operating results and rate of growth; any unknown errors or limitations in the Sendia technology; any third party intellectual property claims arising from the Sendia technology; customer and partner acceptance and deployment of the AppExchange and AppExchange Mobile platforms; interruptions or delays in our service or our Web hosting; our new business model; breach of our security measures; possible fluctuations in our operating results and rate of growth; the emerging market in which we operate; our relatively limited operating history; our ability to hire, retain and motivate our employees and manage our growth; competition; our ability to continue to release and gain customer acceptance of new and improved versions of our CRM service; unanticipated changes in our effective tax rate; fluctuations in the number of shares outstanding; the price of such shares; foreign currency exchange rates and interest rates.

Further information on these and other factors that could affect our financial results is included in the reports on Forms 10-K, 10-Q and 8-K and in other filings we make with the Securities and Exchange Commission from time to time, including our Form 10-K for the fiscal year ended January 31, 2006. These documents are available on the SEC Filings section of the Investor Information section of our website at www.salesforce.com/investor .

Any unreleased services or features referenced in this or other press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements, except as required by law.

Business Mashups: Best of the Web APIs Track: New AppExchange Developer Jonathan Jessup Development Manager

Infopia Introduction

Leader in On-demand eCommerce Solutions

The industry’s most complete on-demand eCommerce solution suite for online merchants:

Marketplace Manager ™

INDUSTRY: eCommerce EMPLOYEES: 43 GEOGRAPHY: Global PRODUCTS USED: Oracle On-Demand, Salesforce. # USERS: 350

Multichannel Selling – Means “Multi-Mashup”

Infopia utilizes API’s from many partners to deliver a complete ‘Inventory to Cash’ solution

Real-Time Inventory

Listings (Price, Promotion, Product, Place)

Website

Marketplaces

Comparison Shopping

Order Mgmt

Customer Mgmt

Fraud Alert

Online Sales Pipeline

Marketplaces

Customers

Products

Market Presence & Shopping Tools Inventory & Merchandising Fulfillment & Service Analysis & Decisions CRM Marketplaces Comparison Shopping ERP Analytics Payment & Shipping

Transforming eCommerce Transactions into Relationships

The Challenge – Taking my Business to eBay

Businesses looking to take advantage of eBay marketplace

Required resources to making this a viable business channel

Keeping this channel in sync with their traditional direct sales efforts.

The Solution –Infopia, salesforce.com, & eBay

Extend the sales reach to the vast eBay online marketplace in a cost effective manner

Optimize customer service by maintaining the complete 360-degree customer visibility

Ecommerce Solution Marketing Service Sales Analytics Operations & Merchandising Fulfillment & Service Market Presence Analysis/ Decisions CRM Solution Online Sales Channels

Keys to Successful API Integration

Language-independent implementation (SOAP XML)

Accessible over standard Internet protocols (HTTPS)

Clear and unambiguous description language (WSDL or XSD)

Full development and sandbox environments

SDK and sample codes

Developer’s Network and Support

eBay API Integration

API to create, revise and process eBay auctions

SOAP XML with complete WSDL

Expansive Developers Network and Support

eBay API Calls:

com.ebay.sdk.ApiCall

com.ebay.soap.eBLBaseComponents.ItemType

com.ebay.soap.eBLBaseComponents.AddItemRequestType

com.ebay.soap.eBLBaseComponents.ReviseItemRequestType

com.ebay.soap.eBLBaseComponents.GetItemTransactionsResponseType

com.ebay.soap.eBLBaseComponents.AddMemberMessageRTQRequestType

Paypal Integration

API to process Paypal Payments

SOAP XML with complete WSDL and SDK

Expansive Developers Network and Support

Paypal API Calls:

com.paypal.sdk.services.CallerServices

com.paypal.soap.api.DoAuthorizationRequestType

com.paypal.soap.api.DoCaptureRequestType

com.paypal.soap.api.DoDirectPaymentRequestType

com.paypal.soap.api.DoExpressCheckoutPaymentRequestType

Google Checkout Integration

Google Payment Processing API

XML Integration with complete XSD and SDK

Good technical contacts and support

Google Checkout API Calls:

com.google.checkout.schema.x2.CheckoutShoppingCart

com.google.checkout.schema.x2.NewOrderNotification

com.google.checkout.schema.x2.RiskInformationNotification

Infopia Web Services API

Allows clients and partners to integrate with Infopia

SOAP XML, SSL, WSDL, SDK, Code Examples, etc.

Secure, client-specific access to Marketplace Manager data

Create, update, retrieve, and synchronize:

Inventory

Orders

Customer data

Infopia Demo

Business Mashups: Best of the Web APIs Track: New AppExchange Developer Charlie Wood Principal [email_address]

The Road to Sync: Feeds and Calendars

July ’05: Spanning Salesforce

RSS/Atom feeds for Salesforce and other AppExchange applications

July ’06: Spanning Salesforce for iCal

Web calendars for Salesforce using the iCalendar format and webcal:// protocol

Requirement: Sync with Google Apps

Customer Feedback

Calendar publishing is good

Two-way sync is better

Google Apps becoming a viable alternative to Microsoft Exchange

Technology Challenge

Differences in protocols, formats, data models

Transparent operation

On-demand sync system

Seamlessly integrates Google Applications with salesforce.com

Speaks each system’s native language

Spanning Sync for Google and AppExchange

How did we address the challenges?

Created a composite AppExchange application

Exposed the user interface in a custom tab

Hosted the sync engine on an external server

Used the AppExchange SOAP API and PHP Toolkit, and the Google Calendar Data API

User Perspective

Salesforce calendar and Google Calendar stay in sync

Key Requirements

Simple

Reliable

Transparent

Key Benefits

Eliminates need to maintain multiple calendars

Enables calendar sharing with non-SFDC users

Enables integration with numerous third-party PIM applications

Developer Perspective: Components

Developer Perspective: Process Flow

Login to Google

Get updated and deleted events

Create/update events

Delete events

Developer Perspective: The Google Bits

GData: The Google Data API

The API for Google Applications

Google Calendar

Blogger

Google Base

Format

Atom 1.0 plus custom namespace extensions

“ Kinds” for specific data types (e.g., calendar events)

Protocol

Atom for reading

Atom Publishing Protocol for writing

OpenSearch for queries

Custom authentication for login to Google accounts

Custom versioning for conflict detection

Login to Google Calendar

ClientLogin (for installed apps), not AuthSub (for web apps)

HTTPS POST login request

Handle responses from Google:

success (HTTP 200)

failure (HTTP 403)

invalid request

CAPTCHA challenge

“ Success” response includes an authentication token, required for all subsequent requests

Get Updated and Deleted Events Using GData

Queries are expressed an HTTP URIs:

http://www.google.com/calendar/feeds/default/private/full?gsessionid=t1tdeGVYHL0&updated-min=2006-10-08T09:00:00-07:00&max-results=1000

Queries return an Atom feed with data in elements from two custom XML namespace extensions (“gd” and “gCal”):

...

<gCal:sendEventNotifications value = "true" />

<gd:recurrence> DTSTART;VALUE=DATE:20060818 DTEND;VALUE=DATE:20060819 RRULE:FREQ=DAILY;INTERVAL=1;UNTIL=20060823;WKST=SU </gd:recurrence>

<gd:eventStatus value = "http://schemas.google.com/g/2005#event.confirmed" />

<gd:transparency value = "http://schemas.google.com/g/2005#event.opaque" />

<gd:reminder minutes = "10" />

...

Updates and Deletes are returned together, with deletes denoted by their status:

<gd:eventStatus value = "http://schemas.google.com/g/2005#event.canceled" />

Create and Update Events Using GData

Specify the event using the GData format :

<?xml version="1.0"?>

<entry xmlns ="http://www.w3.org/2005/Atom" xmlns: openSearch ="http://a9.com/-/spec/opensearchrss/1.0/" xmlns: gd = "http://schemas.google.com/g/2005" xmlns: gCal = "http://schemas.google.com/gCal/2005" >

< id>http://www.google.com/calendar/feeds/default/private/full/73st11emr9vunnde9sb2ggnsug </id>

<category scheme = "http://schemas.google.com/g/2005#kind" term = "http://schemas.google.com/g/2005#event" />

<title type = "text" > Dreamforce Preparty </title>

<content type = "text" > Don't stay out too late! </content>

</content>

<gd:transparency value = "http://schemas.google.com/g/2005#event.opaque" />

<gd:visibility value = "http://schemas.google.com/g/2005#event.default" />

<gd:eventStatus value = "http://schemas.google.com/g/2005#event.confirmed" />

<gd:when startTime = "2006-10-08T21:00:00.000-07:00" endTime = "2006-10-00T00:00:00.000-07:00" >

<gd:reminder minutes = "15" />

</gd:when>

</entry>

To create a new event, use HTTP POST to the feed’s URI

To update an event, use HTTP PUT to the event’s URI

Delete Events Using GData

To delete an event, use HTTP DELETE with the event’s URI:

<?php

$header [] = "Authorization: GoogleLogin auth=" . $this ->authToken;

$header [] = "X-HTTP-Method-Override: DELETE" ;

$ch = curl_init ();

curl_setopt ( $ch , CURLOPT_HTTPHEADER, $header );

curl_setopt ( $ch , CURLOPT_URL, $theEventURI . "?gsessionid=" . $this ->sessionID);

curl_setopt ( $ch , CURLOPT_HEADER, 1 );

curl_setopt ( $ch , CURLOPT_RETURNTRANSFER, 1 );

curl_setopt ( $ch , CURLOPT_POST, 1 );

$tmp = curl_exec ( $ch );

curl_close ( $ch );

?>

GData Optimistic Concurrency (Versioning)

Motivation

To prevent one client from overwriting another’s changes

Implementation

A version ID is appended to every GData entry’s URI:

http://www.google.com/calendar/feeds/default/private/full/k28lgd7n9jgbi220cv4fe5to04/ 63293840053

When a PUT or DELETE is performed, the version in the request is compared to the version of the existing entry

If the versions don’t match, Google responds with HTTP 409 Conflict

Beta

This is still a work in progress

Lessons Learned

Developing for GData feels like developing for AppExchange

No software to install, no biz dev meetings to attend

Develop using your language and tools of choice

Google Calendar Data API is still in beta

Only some data types supported (e.g., no contacts or tasks)

“ Optimistic concurrency” versioning system still in development

Format and protocol docs don’t yet always match behavior

No scripting-level toolkits available yet, so you’ll be writing Java, C#, or raw HTTP requests

AppExchange + Google mashups can be incredibly powerful and relatively simple to create

For More Information

Google Data APIs (Beta) Developer’s Guide

http://code.google.com/apis/gdata/overview.html

Using the Google Calendar Data API

http://code.google.com/apis/gdata/calendar.html

Google Account Authentication

http://code.google.com/apis/accounts/Authentication.html

Google Groups: Google Calendar Data API

http://groups.google.com/group/google-calendar-help-dataapi

Moonwatcher (My Blog)

http://globelogger.com/moonwatcher

Ron Hess Charlie Wood Principal Jonathan Jessup QUESTION & ANSWER SESSION Salesforce.com Spanning Partners Jonathan Jessup Development Manager Developer Marketing

Session Feedback Let us know how we’re doing!

Please score the session from 5 to 1 (5=excellent,1=needs improvement) on the following categories:

Overall rating of the session

Quality of content

Strength of presentation delivery

Relevance of the session to your organization

Save time! Use your cell phone or mobile device to send Feedback via SMS/Text Messaging! Send a message to 26335 In the message body: Session 234, #### For example, “ Session 123, 5555 ” Session ID: 234 Session ID # Scores for 4 categories SMS Voting powered by:

Login Sample Code (Part 1 of 3)

<?php

function authenticate($gcUname, $gcPword, $loginToken, $loginCaptcha) {

$header[] = "Content-type: application/x-www-form-urlencoded";

$postFields = "AccountType=HOSTED_OR_GOOGLE&Email=".urlencode($gcUname)."&Passwd=";

$postFields .= urlencode($gcPword)."&source=Spanning-AppExSync-1&service=cl";

if(strlen($loginToken) && strlen($loginCaptcha)) {

$postFields .= "&logintoken=".$loginToken."&logincaptcha=".$loginCaptcha;

}

$ch = curl_init("https://www.google.com/accounts/ClientLogin");

curl_setopt($ch, CURLOPT_HTTPHEADER, $header);

curl_setopt($ch, CURLOPT_HEADER, 1); // include the header in the output

curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1); // store the output in a variable

curl_setopt($ch, CURLOPT_POST, 1);

curl_setopt($ch, CURLOPT_POSTFIELDS, $postFields);

$tmp = curl_exec($ch);

curl_close($ch);

// parse the response and check for authentication success/failure

$theResponse = $this->parse_response($tmp);

switch($theResponse["code"]) {

case "200": // success

break;

case "403":

$this->handleBadLoginResponse($theResponse["body"]);

break;

default:

$msg = "Unrecognized response status code on attempted Google Calendar authentication. ";

$msg .= "Status code: ".$theResponse["code"]." ";

$msg .= "Body: ".$theResponse["body"]." ";

failWithError($msg);

}

// extract authorization token

$ret = $theResponse["body"];

if(ereg("Auth=(.*) ",$ret,$regs)) {

$this->authToken = $regs[1]; // authenticaion token

} else {

failWithError("Authorization token not found in response from Google Calendar. ");

}

// make subsequent (authenticated) request to Calendar

$ch = curl_init("http://www.google.com/calendar/feeds/default/private/full");

unset($header);

$header[] = "Authorization: GoogleLogin auth=".$this->authToken;

$header[] = "Content-type: application/atom+xml";

curl_setopt($ch, CURLOPT_HTTPHEADER, $header);

curl_setopt($ch, CURLOPT_HEADER, 1); // include the header in the output

curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1); // store the output in a variable

curl_setopt($ch, CURLOPT_POST, 1);

curl_setopt($ch, CURLOPT_FOLLOWLOCATION, 0); // DON'T follow the (expected) redirect

$tmp = curl_exec($ch);

curl_close($ch);

// parse the response and check for authentication success/failure

$theResponse = $this->parse_response($tmp);

switch($theResponse["code"]) {

case "302": // success

break;

default:

$msg = "Unrecognized response status code (not 302) on authenticated request to Google Calendar. ";

$msg .= "Status code: ".$theResponse["code"]." ";

$msg .= "Body: ".$theResponse["body"]." ";

failWithError($msg);

}

// extract session id

$ret = $theResponse["header"]["Location"];

if(ereg("([^?]*).*gsessionid=(.*) ",$ret,$regs)) {

$this->sessionID = $regs[2]; // authentication token

$this->feedURL = $regs[1]; // feed URL

} else {

failWithError("Session ID not found in response from Google Calendar.");

}

debug("Connected to Google and authenticated.");

}

?>

Business Mashups Best of the Web APIs

1 comments

Notes on slide 1

8 Favorites