HourSquare · OAuth Scopes

HourSquare OAuth Scopes

OAuth 2.0 derived

HourSquare publishes 5 OAuth 2.0 scopes via the clientCredentials flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the HourSquare API on a user’s behalf.

Tokens are issued from https://api.hoursquare.com/api/public/v1/oauth/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

Human ResourcesPayrollTime TrackingWorkforce ManagementSoftware-as-a-Service

Scopes: 5 Flows: clientCredentials Method: derived

OAuth endpoints

Token URL
https://api.hoursquare.com/api/public/v1/oauth/token

Flows
clientCredentials

Scopes (5)

Scope	Description	Flows
attendance.read	Read time entries (permission 47)	clientCredentials
attendance.record	Record clock events and completed shifts; set employee external ids (permission 86)	clientCredentials
attendance.reports	Read time reports (permission 49)	clientCredentials
employees.read	Read employees (id, external id, name, email, status) (permission 52)	clientCredentials
leave.read	Read leave balances and requests (permission 72)	clientCredentials

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-11-03'
method: derived
source: openapi/hoursquare-openapi.json
schemes:
- name: OAuth2
  source: openapi/hoursquare-openapi.json
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.hoursquare.com/api/public/v1/oauth/token
  description: 'Client credentials (RFC 6749 §4.4): POST your API key as `client_secret` (or
    as the HTTP Basic password) to the token URL and use the returned token as a Bearer. Tokens
    live 15 minutes. Each operation lists the scope it requires; a key carries the scopes it
    was created with.'
scopes:
- scope: attendance.read
  description: Read time entries (permission 47)
  flows:
  - clientCredentials
  sources:
  - openapi/hoursquare-openapi.json
- scope: attendance.record
  description: Record clock events and completed shifts; set employee external ids (permission
    86)
  flows:
  - clientCredentials
  sources:
  - openapi/hoursquare-openapi.json
- scope: attendance.reports
  description: Read time reports (permission 49)
  flows:
  - clientCredentials
  sources:
  - openapi/hoursquare-openapi.json
- scope: employees.read
  description: Read employees (id, external id, name, email, status) (permission 52)
  flows:
  - clientCredentials
  sources:
  - openapi/hoursquare-openapi.json
- scope: leave.read
  description: Read leave balances and requests (permission 72)
  flows:
  - clientCredentials
  sources:
  - openapi/hoursquare-openapi.json

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/hoursquare-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.