Location Labs

  • Company
  • Products
  • Blog
  • Facebook
  • Twitter
  • YouTube
[icon] Universal Location Service

Universal Location Service

  • Overview
  • My Apps
  • Tutorials
  • Test Tools
  • SDK
  • Developer Guide
  • Billing
  • Support
  • Register
  • Sign In

Developer Guide

  • 1.0 About Veriplace
  • 2.0 Getting Started
  • 3.0 Using the User Discovery API
  • 4.0 Using the Get Location API
  • 5.0 Using the Past Location API
  • 6.0 Using the Verify Permission API
  • 7.0 Using the Permission Delete API
  • 8.0 Using the Get Permissions API
  • 9.0 Using the Invitation API
  • 10.0 Using the Polling API
  • 11.0 Using the Verify Locatability API
  • 12.0 Previous API versions
  • Veriplace XML Schema
  • Disclaimer
  • OAuth Core 1.0 Rev A

Using the Get Permissions API

8.0 Using the Get Permissions API

You can use the Get Permissions API to determine the list of Veriplace user identifiers that are currently granting permission to your application to access location.

Before using the Get Permissions API, you must possess the application-specific Access Token. See section 2.3.1.2 OAuth Credentials for more details.

8.1 About Getting Permissions

Veriplace retains a record of every permission granted by a user to be located by each application, including permissions granted by users without your application's direct knowledge.

Your application can choose to periodically query the current list of permissions to synchronize its state with that of the Veriplace server.

8.2 Getting Permission

To get permissions, submit an HTTP GET to the following URL:

https://veriplace.com/api/1.2/permissions

Requests must be signed using HMAC-SHA1 and the application-specific Access Token.

Requests may optionally specify a "max" parameter to limit the number of results returned. Requests that specify the "max" parameter may also specify a "first" parameter to page through results.

8.3 Successful Requests

On success, you will receive an HTTP 200 ("OK") code and a list of user identifiers. The XML encoding looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<users xmlns="http://veriplace.com/xml/1.2">
  <user id="1378603015410979905"/>
  <user id="7799817486972445687"/>
</users>

The same list in JSON encoding:

{
  "users": [
    { "id": "1378603015410979905" },
    { "id": "7799817486972445687" }
  ]
}

8.4 Unsuccessful Requests

You will receive a HTTP 400 status code if the request was malformed.

Developers

  • Developer Terms of Service
  • Privacy Policy
  • Content Requirements
  • Trademark Schedule
  • Forum

End Users

  • Terms of Service
  • Privacy Policy
  • Support

Follow Us

  • [icon] Facebook
    Facebook
  • [icon] Twitter
    Twitter
  • [icon] YouTube
    YouTube

Location Labs

info@locationlabs.com

© 2010 Location Labs

All rights reserved.