Upscale is changing the way people work.
Api Endpoints for user and organization authentication
Users Description
Organizations API endpoints.
Teams Description
Interact with information related to an individual's active browser session
Returns information about the browser session of the currently logged in user.
| Key | Value(s) | Desc | Required |
|---|---|---|---|
/status
https://getupscale.com/api/v1/session/status
{
status: "success",
response: {
activated: true,
full_name: "Michael E. Karpeles",
submitted: false,
type: "Supervisor",
api_token: "XXX",
username: "mek",
logged: true,
clearance: 15,
id: 1,
email: "m@hackerlist.net",
avatar: "https://s.gravatar.com/avatar/7ca82283af0b65b163dde4f5f5e3fb41?s=250",
orgs: []
}
}
The different Role Value(s)s on Upscale
https://getupscale.com/api/v1/roles
The different Tags on Upscale, which are basically StackOverflows.
https://getupscale.com/api/v1/tags
Standard HTTP status codes are used to communicate the success or failure of a request. A code in the 2xx range indicates success, 4xx indicates an error that resulted from the provided information (e.g. a required parameter was missing, a bank account failed tokenization, etc), 5xx indicates an error with Upscale's servers.
200 ok: resource(s) retrieved successfully.
201 created: resource created.
204 no content: resource deleted.
400 bad request: request is improper and/or malformed.
401 unauthorized: http authentication must be used to access the requested uri.
403 forbidden: not authorized to access the resource at the requested uri.
404 not found: requested uri doesn't exist.
405 method not allowed: http method used is not allowed for the requested uri.
409 conflict: the request was correctly formed but had a logical error.
500, 502, 503, 504 internal server error: something went wrong on Upscale's side.