Use /auths to authenticate a user from your app.


This call is rate limited to one (1) request per user per Service in a five (5) second span and three (3) requests in a sixty (60) second span.


Content Type:application/x-www-form-urlencoded
Accept Types:application/json


Form URL Encoded String with the following control names:


LaunchKey username, user push ID, or end-user identifier for the user being authorized


Service Key of your service. Find this on the Keys tab of your service in the Dashboard.


Optional - Options: [0, 1] - Default: 1 - Flag determining whether this Auth Request is to be designated as a Session. An Auth Request can be designated as a session or transaction based on the needs of your service. Sessions should be used when the User will have the ability to end an active session and log out (e.g. signing in and out of a website or app), whereas transactions are inactive one-way authorizations where the situation doesn't merit the need for the ability to logout/clear (e.g. approving receipt of a package). Sessions are default, but transactions can be specified by sending this value as 0


Optional - Options: [0, 1] - Default: 0 - Flag determining whether this Auth Request is to return a User Push ID.


Optional - Unique ID to match the response; will be generated if not provided


Optional - Text value to be presented to the user when viewing an auth request on their device. The context allows the user to have confidence that they are responding to the correct request.


Optional - Authorization policy for this call. The values provided are in a JSON encoded string. The values of this field will be merged with any static policies set for the service in the Dashboard. They cannot be used to make the static policy less restrictive. The policy object can have the following attributes:


Optional - Object identifying the factor requirements for the request.

requirement:Options: [authenticated, enabled] - To require any factors, authenticated is required.
all:Minimum number of factors required
knowledge:Options[0, 1] - Flag determining whether a knowledge factor is required
inherence:Options[0, 1] - Flag determining whether an inherence factor is required
possession:Options[0, 1] - Flag determining whether a possession factor is required

Optional - List of objects describing auth factors with the following attributes:


Options: [circle code, pin code, bluetooth proximity, geofence] - The type of factor


Options: [true, false] - Boolean flag when true will immediately fail the auth upon failure of the factor and the mobile device will not process any remaining factors.


Options: [forced requirement, allowed] - To require the factor, forced requirement is required.


Integer value representing the priority of the factor being presented to the user.


Optional: Not required for non-geofence factors - Object with the following attributes:


List of location objects with the following parameters:

radius:A decimal value of the radius for a geofence in meters.
latitude:A decimal value of the latitude in degrees for the center of the geofence.
longitude:A decimal value of the longitude in degrees for the center of the geofence.


POST /auths HTTP/1.1
Content-Type: application/x-www-form-urlencoded
Content-Length: hgfdså
Accept: application/json



Status:200 OK


JSON string with the following attributes:

auth_request:string Unique identifier for tracking status of the Auth Request


HTTP/1.1 200 OK
Server: nginx
Date: Sun, 10 Nov 2013 03:56:22 GMT
Content-Type: application/json; charset=UTF-8
Content-Length: 52
Connection: keep-alive
Strict-Transport-Security: max-age=31536000; includeSubdomains

{"auth_request": "4yjuyyg59cqf2s890uhhhx3vmtgv115a"}

Policy JSON Example

Policy example requiring a two factors plus a geofence located at center of the the Taj Mahal with a radius of 60 meters:

    "minimum_requirements": [
            "requirement": "authenticated",
            "all": 2,
            "knowledge": 0,
            "inherence": 0,
            "possession": 0
    "factors": [
            "factor": "geofence",
            "requirement": "forced requirement",
            "quickfail": false,
            "priority": 1,
            "attributes": {
                        "radius": 60.0,
                        "latitude": 27.175,
                        "longitude": 78.0422

User Contributed

LaunchKey links to user contributed code as a resource to its community. LaunchKey does not in any way guarantee or warrant the quality and security of these code bases. User contributed code is supported by the creators. If you do find a link from the site to user contributed code that is malicious or inappropriate in any way, please report that link to LaunchKey immediately and we will investigate the claim. Submit any issue to LaunchKey support at ×