• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
REST APIs in WO applications
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

REST APIs in WO applications


  • Subject: REST APIs in WO applications
  • From: Kalpana Vaka <email@hidden>
  • Date: Mon, 21 May 2012 23:41:38 +0530

Hi All,

 

    We have an urgent requirement from a customer to support REST APIs.  They are using some other system and these APIs are in production now.

They want us to receive these API calls now.   The question is how we can implement these in our WO application.  I am giving an example of the API below.

Thanks for your help! Can anyone help us with this? Can we do this with direct action?

 

 

Method: createUser

 

Input:

 

Parameter Nane

Type

Required*

Description

Notes

partnerId

String

Y

Partner Identifier. i.e. une

 

partnerPassword

String

Y

Password i.e admin@une

 

email      

String

Y

User email

Max 50 chars

password

String

Y

User password

Max 30 chars

firstname

String

Y

User First Name

Max 50 chars

lastname

String

Y

User Last Name

Max 50 chars

birthdate

String

N

User birthdate

dd/mm/yyyyy

cellphone

String

N

User cellphone

Max 10 chars

country

String

Y

Default MX

2 character

regionCode

String

N

ISO Codes

2 character

address   

String

N

User address

Max 255 chars

city

String

N

User City

Max 100 chars

zipcode  

String

N

User Zip Code

Max 10 chars

freetrial

Char

N

[Y|N]

 

subid1 - subid5

String

N

Five parameters (your partnername as part of subid1, any other information as part of subid2 – 5.

 

 

*Required Fields: All the required fields (Y) are mandatory. 

Output:

status: Success/Fail

 

In case of Success:

            userId (unique user id)

            accountId (internal account id for cross-reference purposes)

 

Invoke Example:

 

https://test.com/rest/createUser?partnerId=TESTPARTNER&partnerPassword=PASSWORD123&email=email@hidden&password=pass123&firstname=Terry&lastname=Tester&country=MX&subid1=xyz1&subid2=xyz2&subid3=xyz3&freetrial=y

Output Examples:

 

Success:

 

<createUserResponse>

            <tmResponseCode>000000000</tmResponseCode>

            <message>

                        <accountID>2105033283</accountID>

                        <user_id>email@hidden</user_id>

            </message>

</createUserResponse>

 

The ‘000000000’ value of <tmResponseCode> represents success.

 

Fail:

 

<createUserResponse>

            <detail>

                        <responseCode>100_02_30007</responseCode>

                        <responseMessage>Email id mentioned in profile already exists in database.</responseMessage>

            </detail>

            <tmResponseCode>111111111</tmResponseCode>

</createUserResponse>

 

The ‘111111111’ value of <tmResponseCode> represents failure.

 

Thanks & Regards,

Kalpana.

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: REST APIs in WO applications
      • From: Kieran Kelleher <email@hidden>
  • Prev by Date: Re: REST API with WebObjects
  • Next by Date: Re: REST APIs in WO applications
  • Previous by thread: Re: REST API with WebObjects
  • Next by thread: Re: REST APIs in WO applications
  • Index(es):
    • Date
    • Thread