Retrieve variables available to templates within the given template scope.
Message Templates (0.0.14)
The Message Template API provides the ability to create custom messaging (email, sms) templates that can be used to communicate with network users.
- Create and manage message templates: Allows the creation and management of message templates within specific categories and template scopes that can be used for communication.
- Register usages of templates: Registrations can be created to associated an external resource with a specific template using a custom ID.
- Content Types: Supports
application/jsonandapplication/vnd.ruckus.v1+json - API Version: v0.0.14
- Data Formats: JSON with HATEOAS links for resource navigation
- Pagination: Standard pagination with configurable page sizes
A custom template can be created for use when a new user is assigned a unit in property management. This allows for custom branding or information to be provided to network users.
All API calls require valid authentication via Bearer token in Authorization header. Include the JWT token in the Authorization: Bearer <token> header.
The API uses standard HTTP status codes with detailed error messages in the response body.
All endpoints may return these common error responses:
- 400 Bad Request: Invalid input data or validation errors
- 401 Unauthorized: Missing or invalid authentication
- 403 Forbidden: Insufficient permissions
- 404 Not Found: Requested resource doesn't exist
- 409 Conflict: Resource conflict (e.g., duplicate names)
- 422 Unprocessable Entity: Business rule violations
- 500 Internal Server Error: Unexpected server errors
- RUCKUS One API host for North American region.https://api.ruckus.cloud/templateScopes
- RUCKUS One API host for European region.https://api.eu.ruckus.cloud/templateScopes
- RUCKUS One API host for Asian region.https://api.asia.ruckus.cloud/templateScopes
- Payload
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
No request payload{ "paging": { "totalCount": 0, "page": 0, "pageSize": 0, "pageCount": 0 }, "content": [ { … } ], "_links": { "property1": { … }, "property2": { … } } }
A comma separated list of child resources to include in the response in the format: includes={resource path},{resource path}. Where {resource path} must match the REST API path for that resource underneath the Template Scope. Only individual registrations are allowed. Any resource that is invalid or not found will be silently ignored. For example: includes=registrations/registration.id.1,registrations/registration.id.2
- RUCKUS One API host for North American region.https://api.ruckus.cloud/templateScopes/{templateScopeId}
- RUCKUS One API host for European region.https://api.eu.ruckus.cloud/templateScopes/{templateScopeId}
- RUCKUS One API host for Asian region.https://api.asia.ruckus.cloud/templateScopes/{templateScopeId}
- Payload
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
No request payloadTemplate scope
- application/json
- application/vnd.ruckus.v1+json
A key which can be used by a user interface to locate a localized description of the template scope.
The default template to use for this template scope. This will be used when sending a message if there is no requested template, or the requested template cannot be found.
The list of registrations associated with this template scope.
{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "messageType": "EMAIL", "nameLocalizationKey": "string", "defaultTemplateId": "bee715a2-1763-4940-8b0e-39be16b372e7", "registrations": [ { … } ], "_links": { "property1": { … }, "property2": { … } } }