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 Permission Delete API

7.0 Using the Permission Delete API

You can use the Permission Delete API to revoke your ability to obtain location information for an individual mobile user. If you don’t delete a permission, it will expire only if the user chooses to revoke it.

Before using the Permission Delete API, you must posses a Veriplace user identifier and an Access Token representing the permission that you want to delete.

7.1 About Permissions

Permission is required to obtain the location information of a mobile user. Your application obtains permission using the OAuth process. An individual permission is represented by an Access Token.

Permissions may be deleted in a variety of ways. Some permissions expire immediately after their use, while others can last indefinitely or at least until the user changes their privacy settings.

You can choose to delete a permission. For example, your application may support cancellation of service and you may wish to surrender your rights to obtain location for a user when this happens. This chapter describes how to delete such a permission.

7.2 Deleting Permissions

To delete a permission, submit an HTTP POST or DELETE to the following URL:

https://veriplace.com/api/1.2/users/<userId>/permissions

Requests must be signed using HMAC-SHA1 and the Access Token representing the permission.

7.2.1 Common Failure Conditions

You cannot delete permissions that are not associated with your application or that were already deleted.

7.3 Successful Requests

On success, you will receive an HTTP 200 ("OK") code.

7.4 Unsuccessful Requests

In accordance with the HTTP Response Codes section of the OAuth specification, you will receive an HTTP 400 ("Bad Request") or 401 ("Unauthorized") code if something went wrong with the OAuth signature.  In some cases, a 401 error code will be accompanied by the reason phrase "Invalid / non-monotonic timestamp", which is commonly a sign that your system clock is misconfigured.

You will also receive a 401 error code if the permission cannot be deleted or was already deleted.

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.