Free api software for linux

eBay::API is a Perl SDK for eBay Web services Interface.

SYNOPSIS

# 1. GeteBayOfficialTime use eBay::API::XML::Call::GeteBayOfficialTime;
my $pCall = eBay::API::XML::Call::GeteBayOfficialTime->new();
$pCall->execute();
my $sOfficialTime = $pCall->getEBayOfficialTime();
# 2. GetUser use eBay::API::XML::Call::GetUser; use eBay::API::XML::DataType::Enum::DetailLevelCodeType;
my $pCall = eBay::API::XML::Call::GetUser->new();
$pCall->setDetailLevel( [eBay::API::XML::DataType::Enum::DetailLevelCodeType::ReturnAll] );
$pCall->setUserID(userId);
$pCall->execute();

my $pUser = $pCall->getUser();
my $sStatusCode = $pUser->getStatus();
my $sSiteCode = $pUser->getSite();
# 3. VerifyAddItem use eBay::API::XML::Call::VerifyAddItem; use eBay::API::XML::DataType::ItemType; use eBay::API::XML::DataType::CategoryType; use eBay::API::XML::DataType::Enum::CountryCodeType; use eBay::API::XML::DataType::Enum::CurrencyCodeType; use eBay::API::XML::DataType::Enum::ListingTypeCodeType; use eBay::API::XML::DataType::Enum::BuyerPaymentMethodCodeType;
my $pItem = eBay::API::XML::DataType::ItemType->new();
$pItem->setCountry(eBay::API::XML::DataType::Enum::CountryCodeType::US);
$pItem->setCurrency(eBay::API::XML::DataType::Enum::CurrencyCodeType::USD);
$pItem->setDescription(item description.);
$pItem->setListingDuration(eBay::API::XML::DataType::Enum::ListingTypeCodeType::Days_1);
$pItem->setLocation(San Jose, CA);
$pItem->setPaymentMethods(eBay::API::XML::DataType::Enum::BuyerPaymentMethodCodeType::PaymentSeeDescription);
$pItem->setQuantity(1);
$pItem->getStartPrice()->setValue(1.0);
$pItem->setTitle(item title);

my $pCat = eBay::API::XML::DataType::CategoryType->new();
$pCat->setCategoryID(357);
$pItem->setPrimaryCategory($pCat);

my $pCall = eBay::API::XML::Call::VerifyAddItem->new();

$pCall->setItem($pItem);
$pCall->execute();

$sItemId = $pCall->getItemID()->getValue();

Clickatell SMS API provides a tool for sending SMS messages using the Clickatell gateway.
It provides support to authenticate to this service and query for the current account balance.
This class use the fopen or CURL module to communicate with the gateway via HTTP/S.
Enhancements:
- Fixed bug in function encode_message (tnx Neil)

FEAR::API is a tool that helps reduce the time you spend creating site scraping scripts and helps you do it in a much more elegant way.
FEAR::API combines many strong and powerful features from various CPAN modules, such as LWP::UserAgent, Template::Extract, WWW::Mechanize, Encode, HTML::Parser, etc.
Enhancements:
- This release adds allow_domains() and deny_domains().

Wikipedia API is a simple API to embed Wikipedia content dynamically on a Web site.

Wikipedia is an online encyclopedia in which the user community is encouraged to submit information for its entries. Wikipedia is unique in that it is free to the public, the content is fairly well moderated, and its content is licensed under the GFDL (GNU Free Documentation License); therefore, all of its text can be copied, modified, and used any way you see fit.

The only stipulation to using its text, is that the names of the original authors must remain intact. KillerTux.com is currently embedding some of the relevant entries in its own site and has decided to make the API open for public use. It is a simple implementation and should be easy to use. If you are a webmaster and would like to use KillerTux.coms Wikipedia API, this is the place to learn how to do it.

What is an API

An API is an application programming interface with which external applications can communicate with. The syntax and usage of the API dictates the type of data, format, and other specifics of the information to be exchanged. In this case, the API is a simple call to KillerTux.coms web server via the HTTP protocol.

Wikipedia API usage

The URL for the API is "http://scrapers.killertux.com/wikipedia-api.php". It uses the get request method and only has 3 parameters. These parameters are as follows:

wikititle=
wikiformat=[html | text]
wikiimages=[yes | no ]

The wikititle value is the name of the Wikipedia entry you are looking for, in Wikipedias variable entry. This can be found by going to Wikipedia.org and finding an entry. The name is the last part of the URL. For instance, the Wikipedia entry for "Computer Program" is "http://en.wikipedia.org/wiki/Computer_Program". Notice the space is an underscore in the URL. Defining the wikititle value for this API would look like this: wikititle=Computer_Program. This value must be specified. A sample API call would be "http://scrapers.killertux.com/wikipedia-api.php?wikititle=Computer_Program". The wikiformat value currently has two possible values: html and text. html is the default if no value is specified. If you use HTML format, it is recommended that a style sheet be used, although it may not be necessary.

A sample CSS is provided here. The text format option strips all HTML code from the document and returns plain text formatted at 80 characters per column. A sample API call would be "http://scrapers.killertux.com/wikipedia-api.php?wikititle=Computer_Program&wikiformat=html". The wikiimages value is only valid for HTML format; images for the text format are disabled. Image source locations are preserved and images are loaded from Wikipedia, not KillerTux.com. If wikiimages=no is selected, all images and captions will be striped from the document, while other HTML code should remain intact such as links to other articles. A sample API call would be "http://scrapers.killertux.com/wikipedia-api.php?wikititle=Computer_Program&wikiimages=no".

Star Asterisk API is a high performance API that connects to the manager interface of Asterisk or to AstManProxy.
Star Asterisk API is easy to use, object-oriented, and easy to extend to suit your particular requirements.
Main features:
- Easy to use -- Simple php
- Easy to extend -- Object oriented approach
- High performance -- Handles High volume of traffic

XML::API::WIX2 is a WIX source file generation through an object API.

SYNOPSIS

As a simple example the following perl code:

use XML::API;
my $m_wxs = new XML::API(doctype => WIX2, encoding => UTF-8);

$m_wxs->Product_open({
Id => 12345678-1234-1234-1234-123456789012,
Name => Test Package,
Language => 1033,
Version => 1.0.0.0,
Manufacturer => Microsoft Corporation,
});
$m_wxs->Package({
Id => 12345678-1234-1234-1234-123456789012,
Description => My first Windows Installer package,
Comments => This is my first attempt at creating a Windows Installer database,
Manufacturer => Microsoft Corporation,
InstallerVersion => 200,
Compressed => yes,
});
$m_wxs->Media({ Id =>1, Cabinet => product.cab, EmbedCab => yes});
$m_wxs->Directory_open({ Id => TARGETDIR, Name => SourceDir});
$m_wxs->Directory_open({ Id => "ProgramFilesFolder", Name => "PFiles"});
$m_wxs->Directory_open({ Id => "TESTFILEPRODUCTDIR", Name => "TFolder", LongName => "TestFolder"});
$m_wxs->Component_open({ Id => License, Guid => 12345678-1234-1234-1234-123456789012});
$m_wxs->File({ Id => "License", Name => "License.rtf", DiskId => "1", Source => "License.rtf"});
$m_wxs->Component_close();
$m_wxs->Directory_close();
$m_wxs->Directory_close();
$m_wxs->Directory_close();
$m_wxs->Feature_open({ Id => License, Title => License files, Level => 1});
$m_wxs->ComponentRef({ Id => License });
$m_wxs->Feature_close();
$m_wxs->Property({Id => "WIXUI_INSTALLDIR", Value => "TESTFILEPRODUCTDIR"});
$m_wxs->UIRef({Id => "WixUI_Mondo"});
$m_wxs->Product_close();
$m_wxs->_print;

will produce the following nicely rendered output:

< ?xml version="1.0" encoding="UTF-8" ?>

< Wix xmlns="http://schemas.microsoft.com/wix/2003/01/wi">
< Product Id="12345678-1234-1234-1234-123456789012" Language="1033" Manufacturer="Microsoft Corporation" Name="Test Package" Version="1.0.0.0">
< Package Comments="This is my first attempt at creating a Windows Installer database" Compressed="yes" Description="My first Windows Installer package" Id="12345678-1234-1234-1234-123456789012" InstallerVersion="200" Manufacturer="Microsoft Corporation" />
< Media Cabinet="product.cab" EmbedCab="yes" Id="1" />
< Directory Id="TARGETDIR" Name="SourceDir">
< Directory Id="ProgramFilesFolder" Name="PFiles">
< Directory Id="TESTFILEPRODUCTDIR" LongName="TestFolder" Name="TFolder">
< Component Guid="12345678-1234-1234-1234-123456789012" Id="License">
< File DiskId="1" Id="License" Name="License.rtf" Source="License.rtf" />
< /Component> < !-- Guid="12345678-1234-1234-1234-123456789012" Id="License"-->
< /Directory> < !-- Id="TESTFILEPRODUCTDIR" LongName="TestFolder" Name="TFolder"-->
< /Directory> < !-- Id="ProgramFilesFolder" Name="PFiles"-->
< /Directory> < !-- Id="TARGETDIR" Name="SourceDir"-->
< Feature Id="License" Level="1" Title="License files">
< ComponentRef Id="License" />
< /Feature> < !-- Id="License" Level="1" Title="License files"-->
< Property Id="WIXUI_INSTALLDIR" Value="TESTFILEPRODUCTDIR" />
< UIRef Id="WixUI_Mondo" />
< /Product> < !-- Id="12345678-1234-1234-1234-123456789012" Language="1033" Manufacturer="Microsoft Corporation" Name="Test Package" Version="1.0.0.0"-->
< /Wix> < !-- xmlns="http://schemas.microsoft.com/wix/2003/01/wi"-->

POE::API::Peek is a Perl module to peek into the internals of a running POE environment.

POE::API::Peek extends the POE::Kernel interface to provide clean access to Kernel internals in a cross-version compatible manner. Other calculated data is also available.

My intention is to provide massive amounts of internal data for use in POE debugging.

WARNING

This version of this module is certified against POE version 0.38 and above. It will fail on any other POE version.

Further, this module requires perl v5.6.1 or above.

METHODS

new

my $api = POE::API::Peek->new();

Returns a blessed reference. Takes no parameters.

id

my $foo = $api->id();

Obtain the unique id for the kernel. Takes no parameters. Returns a scalar containing a string.

KERNEL UTILITIES

is_kernel_running
if($api->is_kernel_running) {
# do stuff...
}

Tell if the POE Kernel is running and active. Returns 1 if the Kernel is running and 0 if it is not.

active_event
my $event = $api->active_event();

Get the active event name. Returns a string containing the event name.

kernel_memory_size
my $size = $api->kernel_memory_size();

Get the memory footprint of the kernel and consequently the entire POE environment. See the Devel::Size documentation for several caveats involved in this metric.

event_list
my $events = $api->event_list();

Gets the list of events for the whole POE environment. Returns a hash with the session IDs as the keys and a list of events as the values.

which_loop
my $loop_name = $api->which_loop();

Tell which Loop POE has decided to use. Returns the string name of the Loop module.