Api?

[adultzone]

Can anyone teach me this, since I am expert when it comes to email marketing because of help in GFY and other sources now I want to know about API?

[BestXXXPorn]

What do you want to know about APIs? Implementing someone else's or creating one for others to implement?

[adultzone]

Originally Posted by BestXXXPorn

What do you want to know about APIs? Implementing someone else's or creating one for others to implement?

Like for example, xprofiles has an API code how would you generate traffic in there and how would you create an API in there as well.

[cooldude7]

api is nothing but just a predefined field names and other specs and you just implemenet it in your submission form, so when user fills ur form and submits it, the details get posted to the xprofiles server also., imho.

[BestXXXPorn]

Originally Posted by adultzone

Like for example, xprofiles has an API code how would you generate traffic in there and how would you create an API in there as well.

I think defining what an API is will give you a better idea of how you can leverage it for your own needs.

Application Programming Interface (API). APIs allow third party developers to access any given application (in this case a web application) without using a "view". When a developer makes an API available they are allowing third parties direct access to their data in a streamlined manner. Some offer read only while others offer both read and write. Since Xprofiles appears to be, essentially, a dating site, I'll use examples from the dating industry (which I worked in for years).

One of the main reasons to use an API for many people promoting dating sites is so that they can maintain their own branding / look and feel during the entire signup process. In this case you would create and host your own sign up pages but rather than writing to your own database, you are, in a way, using the API to write to the dating site's database. This not only allows you to not lose the visitor before the account is complete but also allows you to do your own experimentation in order to create the most optimized experience for your users. You may find that having ALL the required information on one page is the best for your traffic or you may find that having three smaller steps is the best for your traffic. Using the API allows you to tailor the visitor experience and perform your own AB tests.

If you were to immediately forward the user on to xprofiles or just link to xprofiles you have no control over the signup process.

Other uses:

If you promote three different dating sites you could construct your own site to acquire all the needed information for all three sites in one signup process. At the end of the signup process you might prompt the user and say, "which of these three sites would you like to signup for" with all three checked by default. Then, once they submit that final page, on the back end, you would interface with all three APIs and create three accounts and allow the user to go checkout all three. If you were not using the API you would most likely just link them to site in a new window and HOPE they come back to check out the other sites.

Another use stems from already having a large bank of user information. If you already store all the information required to create an account at xprofiles (or another adult dating site,) you might do a mailing out to all your users saying, "One click signup for dating site X". If the user clicks that link you interface with the API, create their account, and then just forward the user right into xprofiles already logged in (if they support autologin on account creation).

I hope those examples help to illustrate the strength of using an API with a few real world examples. Best of luck!