Developers' Blog

We've recently launched some great new end points for our API.  Following the guidelines within our updated API Reference it is now possible for developers to include Top Lists, Field Reports, Blogs, Pictures and Movies in their own applications.

Use Top Lists and Field Reports to create your own punter guide complete with ranking list and detailed reviews. Or use Blogs to create the new Tumblr for Adults.

Always wanted to have you own tube site?  Use our new Movies API to build a great tube site for any niche you like and earn money with our referral program.

Check out our updated API Reference and start developing something great today.  If you have a business proposal or joint development idea, feel free to suggest it.

AdultWork.com members can rest assured that their content and sales income is managed in exactly the same way as with the main AdultWork.com Site.  Nothing in the Developers Area or API works any differently to the main site.  E.G. someone views a your movie on a developer site - the client pays the price you set and you receive the same.  All that happens is that the developer will get a referring income when referring new customers.

To help developers get the very best out of the AdultWork.com API, we have written this small blog that briefly details some of the good practices that should be followed when it comes to consuming the API.

One of the most common implementations that the API lends itself to is a Profile Listings directory-type application or website. The two main API endpoints that developers would use are /search/searchProfiles and /profile/getProfileDetails.

If a developer chooses to import and cache API data on their own servers we would highly recommend that the getProfileDetails endpoint is only requested on demand - when the end-user chooses to view more information for a specific profile. The response data from the API should be cached with a TTL (Time To Live) and any subsequent end-user requests for that specific profile should then be served from the developer's local cache until the TTL expires and a new getProfileDetails API request is required.

Caching data from the searchProfiles endpoint should be implemented with the ProfilesPerPage request property set to its maximum of 100, and with other criteria such as IsEscort set to true. The more criteria a developer specifies, the faster the API will respond.

Developers should be aware that caching data from the AdultWork API for long periods of time will likely result in the data being out of date or irrelevant. Profiles are added, removed and modified on the AdultWork.com Platform 24 hours a day, 7 days a week, so this is something to bear in mind when deciding the duration of a cache's TTL.

It is no longer possible to connect to any endpoints, platform or API using http://.  All calls must now use https://.

Show your Free Gallery, Private Gallery and Movies on your own website.

Two new widgets have been released that allow you to monetise your own website or blog by embedding your AdultWork.com Galleries and/or Movies into them.

Visitors to your site can now view your free gallery, subscribe to your private gallery or view your movies all without leaving your site.

Using the movie plugin you could actually set-up your own clip store to sell movie clips of any AdultWork.com member, where they get paid as normal, and you earn via the referral scheme.

Have a look at the new plugins on the Wizards & Tools Page.