Apigee adds push messaging capabilities to API platform. Facebook launches local currency API, ending Facebook credits. Plus: Google CalDAV API remains public, Box announces compensation program and SDKs and 6 new APIs.
Targeted Notifications Now Available Through Apigee Platform
Apigee, the company with an API platform designed to help developers design, build, manage and deliver APIs and Apps, has added push messaging to its platform.
According to the press release, one client Ignite, a mobile app development studio, exemplifies why they find the service particularly useful. Apigee explained why:
"The Apigee platform makes it easy to reach customers through APIs, apps, and data, and push notifications give developers a powerful tool to create even more meaningful engagements," said Ed Anuff, head of product strategy at Apigee. "Sharing information directly with a carefully targeted audience has proven to be the most effective way to connect with customers. With Apigee, developers can create context-sensitive push notifications that take advantage of data stored in Apigee. This integration enables highly focused, context-aware push campaigns -- such as notifications sent only to users in a specific geographic location or to your 'most loyal' users."
The notifications are delivered through APIs. In an interesting twist, notifications can be contextually relevant based on factors like location. This is made possible by user stored data in Apigee App Services. Built in analytics are available to measure the impact of campaigns. And this can all be deployed on a massive scale. More information on using the API is available on their developer site.
Facebook ending Credits, Replacing with Local Currency Payments
According to Jonathan Espinosa, of InsideFacebook, Facebook is ending Facebook credits September 12 and replacing it with a local currency payments API it just launched.
"Through the local currency payments API, Developers will be able to set more granular and consistent prices for non-U.S. users and price the same item differently on a market-by-market basis, as opposed to pricing their virtual goods in $0.10 USD increments as was required when Credits became mandatory in July 2011. This also eliminates any confusion that resulted from users trying to think about conversion rates for dollars, Credits and in-game currency."
According to the Facebook documentation, this change has four main benefits: faster performance, international pricing, local currencies (meaning users don't have to perform those mental currency conversion gymnastics when they want to buy from someone selling from another country), and dynamic pricing (you can change what you charge).
As of now, developers have a 90 day time period to integrate the new API (which is that September 12 date). After that, Facebook credits are no longer accepted.
API News You Shouldn't Miss
- Box Announces Developer Compensation Program and New SDKs
- Apigee Adds Push Messaging Capabilities to Its Leading API Platform
- Google Backtracks On Its CalDAV API “Spring Cleaning” And Launches CardDAV API
- Facebook launches local currency payments API, will officially end Facebook credits September 12
6 New APIs
Today we had 6 new APIs added to our API directory including a qr code management platform, a missed call verification service, a multilingual online dictionary and translation memory service and a new south wales government archives and records service.Below are more details on each of these new APIs.
AzonMobile QR Code API: AzonMobile QR Code Management and Tracking platform is a product built to help businesses generate, manage, and track QR Codes. The AzonMobile QR Code API provides developer access to the full functionality of the AzonMobile platform. Supported calls include QR Code generation, QR Code and campaign management, and analytics. The API can be used to generate QR Codes with specified shapes and foreground/background images. The API accepts XML formatted HTTP Post calls and returns XML formatted responses.
Dial2Verify API: Dial2Verify is a free, cloud-based, missed call notification service built around an API that enables users to build call verification based applications. The Dial2Verify API allows missed calls to be forwarded to CRM applications, remote URLs, E-mail addresses, and much more. The API accepts HTTP calls containing a telephone number to be verified and responds with a JSON object or image response.
Glosbe API: Glosbe is a multilingual online dictionary and translation memory. The translation memory is a database of previously translated sentences and phrases. The Glosbe API offers developer access to dictionary translations and translation memories. The API can also be used to add a translation to the Glosbe data. XML and JSON formatted responses are supported, including JSONP for callback.
NSW State Records API: NSW State Records is the New South Wales Government’s archives and records management authority. With over one million entries, it is also NSW’s largest dataset. The NSW State Records API provides developer access to the entire catalog, including full search functionality. All API responses are available in XML or JSON format. Some methods support additional formats, such as MODS.
Quomage API: Quomage is a simple tool for creating a shareable image out of a selection of text. Users can edit the image by choosing the text's font, size, color, alignment, background color, etc. Once created, the image can be downloaded and shared. The Quomage API gives users programmatic access to these functions using REST calls with responses given in JSON.
U.S. Department of State Office of the Historian Ebook Catalog API: The U.S. Department of State Office of the Historian Ebook Catalog contains all ebooks from the Foreign Relations of the United States series, the official historical record of significant foreign policy decisions and diplomatic activity.
This RESTful API allows developers to embed the catalog in 3rd party applications and to locate download links to the ebooks and their cover images. The API uses the Open Publication Distribution System Catalog. The API supports HTTP GET calls and returns XML formatted responses. No authentication required.