The service implements captcha to prevent bots and automated scripts from submitting forms and using other website resources, typically for the purpose of posting spam messages. Unlike services using distorted images, textCAPTCHA posts random, text-based questions, such as easy arithmetic problems or logic puzzles, which users must correctly solve to proceed. Bots unable to interpret the meaning of the text are prevented from continuing.
API methods support requests for questions and MD5 hashes of any permitted answers.
Showing posts with label security Api. Show all posts
Showing posts with label security Api. Show all posts
Thursday, January 12, 2012
Saturday, December 31, 2011
I'm Human API
The I'm Human API is "where humanity wins the fight against machines," according to elxsy.com, the provider of the service. I'm Human is a visual CAPTCHA service which responds with a word, a grid of up to 25 images and the grid numbers which correspond to the correct answers. Humans must select the images that match the words and your application compares the results to the correct answer from the I'm Human API.
I'm Human: Highlights
Summary
Visual CAPTCHA service
Category
Security
Tags
captcha security
Protocols
REST
Data Formats
JSON
API home
http://www.elxsy.com/imhuman/api/
I'm Human: Highlights
Summary
Visual CAPTCHA service
Category
Security
Tags
captcha security
Protocols
REST
Data Formats
JSON
API home
http://www.elxsy.com/imhuman/api/
Google OpenID API
The Google OpenID API lets third-party web sites and applications let visitors sign in using their Google user accounts. The OpenID standard allows users to nor have to set up separate login accounts for different web sites, and conversely, frees web site developers from the task of managing login information and security measures. OpenID achieves this goal by providing a framework in which users can establish an account with an OpenID provider, such as Google, and use that account to sign into any web site that accepts OpenIDs. This page describes how to enable a web site or application to accept a Google user account for federated login.
Google OpenID: Highlights
Summary
OpenID login for Google account users
Category
Security
Tags
OpenID security identity
Protocols
REST
Data Formats
XML
API home
http://code.google.com/apis/accounts/docs/OpenID.html
Google OpenID: Highlights
Summary
OpenID login for Google account users
Category
Security
Tags
OpenID security identity
Protocols
REST
Data Formats
XML
API home
http://code.google.com/apis/accounts/docs/OpenID.html
OneLogin Api
The OneLogin API allows developers to interact with the OneLogin service. OneLogin provides an easy-to-use single sign-on solution for businesses that embrace cloud computing. OneLogin eliminates the need for employees to remember strong passwords and saves them time because they can log into applications with a single click. OneLogin's API supports five basic operations for each entity: read, list, create, update and delete. It uses RESTful protocol and responses are formatted in XML.
OneLogin: Highlights
Summary
Single sign-on solution
Category
Security
Tags
security enterprise cloud sbweb
Protocols
REST
Data Formats
XML
API home
http://support.onelogin.com/entries/113327-introduction
OneLogin: Highlights
Summary
Single sign-on solution
Category
Security
Tags
security enterprise cloud sbweb
Protocols
REST
Data Formats
XML
API home
http://support.onelogin.com/entries/113327-introduction
Google safe browsing API
Reminder: Safe Browsing version 1 API turning down December 1
In May Google announced that Google are ending support for the Safe Browsing protocol version 1 on December 1 in order to focus our resources on the new version 2 API and the lookup service. These new APIs provide simpler and more efficient access to the same data, and they use significantly less bandwidth. If you haven't yet migrated off of the version 1 API, Google encourage you to do so as soon as possible. Our earlier post contains links to documentation for the new protocol version and other resources to help you make the transition smoothly.
After December 1, Google will remove all data from the version 1 API list to ensure that any remaining clients do not have false positives in their database. After January 1, 2012, Google will turn off the version 1 service completely, and all requests will return a 404 error.
Thanks for your cooperation, and enjoy using the next generation of Safe Browsing.
In May Google announced that Google are ending support for the Safe Browsing protocol version 1 on December 1 in order to focus our resources on the new version 2 API and the lookup service. These new APIs provide simpler and more efficient access to the same data, and they use significantly less bandwidth. If you haven't yet migrated off of the version 1 API, Google encourage you to do so as soon as possible. Our earlier post contains links to documentation for the new protocol version and other resources to help you make the transition smoothly.
After December 1, Google will remove all data from the version 1 API list to ensure that any remaining clients do not have false positives in their database. After January 1, 2012, Google will turn off the version 1 service completely, and all requests will return a 404 error.
Thanks for your cooperation, and enjoy using the next generation of Safe Browsing.
Subscribe to:
Posts (Atom)