Source
API documentation — Robin
Checked for Robin on 5 Nov 2026
- Page
- https://docs.robinpowered.com/docs/getting-started
- Checked
- 5 Nov 2026, 14:11 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:14dcecb7222a1cc46f6253d65a4b00ba12f4ba83046e5fecd11b635e5b2d6b68
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Base URL Report an error
“All requests should be made to https://api.robinpowered.com/v1.0. Please note that this may change with future releases of the API.”
-
Authorization header Report an error
“Every API request must contain an Authorization header with a valid access token.”
-
Token source Report an error
“Log into the web dashboard and generate a new token via your team's integration settings. (Note: You must be an administrator)”
-
Response structure Report an error
“All API responses share a basic JSON structure. The response is always an object with two properties meta and data and a conditional third property, paging.”
-
Pagination Report an error
“"paging": { "page": 1, "per_page": 10 }”
-
Deprecated endpoints Report an error
“The GET /free-busy/spaces endpoints will be removed some time in the future. Please use the POST /free-busy/spaces endpoint instead.”
-
Deprecated event properties Report an error
“Event properties started_at and ended_at will be removed some time in the future. Please use start and end instead.”
-
Deprecated include submodel Report an error
“The ?include=amenities submodel for spaces will be removed some time in the future. Please use ?include=space_amenities instead.”
-
Http methods Report an error
“GET Retrieves a resource POST Creates a resource PUT Creates or replaces a resource PATCH Updates an existing resource DELETE Removes a resource”
-
Response codes Report an error
“200 SUCCESS The response completed successfully 201 CREATED The request was a successful and a new resource was created as a result. Error: Response Code Title Meaning 400 BAD_REQUEST There was an error in the request parameters. This error is most commonly send when trying to create or modify a resource with invalid attributes. 401 UNAUTHORIZED The Authorization header is missing or invalid. 403 FORBIDDEN The authorized entity is not permitted to view or modify a resource. 404 NOT_FOUND The resource does not exist.”
-
API scope Report an error
“Robin's API gives developers the power to interact with their team's data (locations, spaces, presence, etc.) and build third-party applications to extend Robin's capabilities.”
-
Sub resources Report an error
“?include=space_amenities”
-
Analytics API Report an error
“Analytics API”
-
Universal presence connector Report an error
“Universal Presence Connector”
1 fact read from this page is not shown because it could not be confirmed on the page as captured.
Scores citing this record
- The Microsoft 365 Administrator Occupancy analytics & employee privacy
- The Microsoft 365 Administrator Integrations, identity & administration
- The Office Manager Occupancy analytics & employee privacy
- The Office Manager Integrations, identity & administration
- The People Lead Occupancy analytics & employee privacy
- The People Lead Integrations, identity & administration
- The Skeptic Occupancy analytics & employee privacy
- The Skeptic Integrations, identity & administration
- The Workplace Manager Occupancy analytics & employee privacy
- The Workplace Manager Integrations, identity & administration
- The Works Council Member Occupancy analytics & employee privacy
- The Works Council Member Integrations, identity & administration