Loading ...

REST API: Get User Space IDs | Axero Documentation

Home » axero documentation » Wiki » Documentation » REST API Overview » REST API: Spaces » REST API: Get User Space IDs
Axero Documentation  Wiki
Public Space
Activity Stream Content
Version 39

REST API: Get User Space IDs

0 
 /5
0 (0votes)
Open API Guide
GET/api/users/{UserID}/spaces/ids

Fetches all the space IDs of the user.

Request

Request Header

HeaderRequiredValueDescription
AuthorizationYESBearer YOUR_TOKENBearer token for the authenticated user. Learn how to create Bearer tokens.

Required Parameters

ParameterTypeRequiredLocationDescription
UserIDIntegerYESPathUnique identifier for a particular user
StatusIntegerYESQuerySpecifies the status of the spaces to be returned. Pending Workflow = 0, Published = 1, Declined = 3, All = 7.

Example

Request Header

Authorization: Bearer YOUR_TOKEN

Request URL

https://your-site.com/api/users/376/spaces/ids?status=0

Success Response

{
  "IsError": false,
  "ResponseMessage": "",
  "ResponseData": [
    291
  ]
}

Error Response

{
  "Message": "No HTTP resource was found that matches the request URI 'https://your-site.com/api/users/804/spaces/ids'."
}

Error Handling

Status CodeLikely CauseNext Action
400 Bad RequestOne or more required fields are missing or invalid. (userID, status)Verify the request payload against the required parameters.
401 UnauthorizedMissing or invalid Bearer token.Check token validity. Learn how to create Bearer tokens →
403 ForbiddenUser does not have sufficient permissions.Confirm the user has the required roles for this action.
500 Server ErrorInternal failure.Retry later.
404 or 405A required query parameter was left out, so the request matched a different action or none: the message reads No HTTP resource was found or The requested resource does not support http method.Send every required query parameter; the message is not about the resource.

Rate Limits

While Axero does not enforce hard rate limits by default, we recommend the following best practices to ensure optimal performance:

  • Sustained Request Rate: Do not exceed 5 API calls per second
  • Sequential Processing: Wait for each request to complete before sending the next in automated workflows
  • Concurrent Connections: If parallel processing is required, limit to 3 or fewer simultaneous requests
  • Response Timeout: Ensure API responses complete within 15 seconds during testing

Axero may implement temporary rate restrictions if excessive API usage affects overall site performance. For high-volume integrations, contact Axero to discuss your requirements.

Wiki Index

Pages