User Service Reference ====================== .. http:post:: https://users.authentise.com/users/ Create a new user. :header Location: The URI of the user that was created **Example request** .. sourcecode:: javascript POST https://users.authentise.com/users/ Content-Type: application/json { "email" : "kenny@powers.com", "name" : "Kenny Powers", "password" : "kpow-was-here", "username" : "kpowers", "address" : "kpowers house", "company" : "Jefferson Davis Middle School", } Location: https://users.authentise.com/users/25a6307b-ca76-43fb-924c-6252c133adcd/ .. http:get:: https://users.authentise.com/users// Get information about a user. :>json string email: The first email address of the user :>json string name: The name of the user :>json string password: The raw text of the password for the user. This will not be stored by the server so remember it :>json string username: The username of the user. This is used for authenticating and uniquely identifying the user :header Location: The URI of the user that was created **Example request** .. sourcecode:: javascript POST https://users.authentise.com/groups/ Content-Type: application/json { "description" : "Sports talk show", "name" : "The Sports Sesh", } Location: https://users.authentise.com/gropus/f74003ad-9942-42fc-b68c-2ce115baf472 .. http:get:: https://users.authentise.com/groups/ Get information about a group :>json string name: The name of the group :>json string description: A description of the group :>json string uuid: The uuid of the group. This should be turned into a URI **Example response** .. sourcecode:: javascript GET https://users.authentise.com/groups/f74003ad-9942-42fc-b68c-2ce115baf472 Content-Type: application/json { "description" : "Sports talk show", "name" : "The Sports Sesh", "uuid" : "f74003ad-9942-42fc-b68c-2ce115baf472" } .. http:post:: https://users.authentise.com/permissions/ Create a new permission. A permission ties a user or group (called a ``holder``) to an arbitrary object via a namespace and a right. Namespaces allow different services to avoid collisions and only query on their own rights. From the standpoint of the service each of these properties is a meaningless string. :header Location: The URI of the permission that was created **Example request** .. sourcecode:: javascript POST https://users.authentise.com/permissions/ Content-Type: application/json { "holder" : "https://users.authentise.com/users/6f9ba4a0-bc52-4884-9491-a4dc29768163", "namespace" : "models", "object" : "https://models.authentise.com/models/b507828d-9473-4702-a0c5-6fe737ad2d8d/", "right" : "frombulate" } Location: https://users.authentise.com/permissions/c688d4cc-0c5b-4200-af39-bca6fa3573a3/ .. http:get:: https://users.authentise.com/permissions// Get information about a permission :>json string holder: The URI of the object that holds the right, usually a group or user :>json string namespace: The namespace of the permission, usually identifies the service that will respect the permission :header Location: The URI of the membership that was created .. http:get:: https://users.authentise.com/memberships// Get information about a membership :