Skip to content

Message Templates (0.0.14)

Overview

The Message Template API provides the ability to create custom messaging (email, sms) templates that can be used to communicate with network users.

What This API Does

  • 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.

Technical Details

  • Content Types: Supports application/json and application/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

Example Use Case

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.

Authentication

All API calls require valid authentication via Bearer token in Authorization header. Include the JWT token in the Authorization: Bearer <token> header.

Error Handling

The API uses standard HTTP status codes with detailed error messages in the response body.

Common Error Responses

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
Download OpenAPI description
Languages
Servers
RUCKUS One API host for North American region.
https://api.ruckus.cloud
RUCKUS One API host for European region.
https://api.eu.ruckus.cloud
RUCKUS One API host for Asian region.
https://api.asia.ruckus.cloud

Variables

Retrieve variables available to templates within the given template scope.

Operations

Template Registrations

Retrieve template registrations.

Operations

Template Scope

Retrieve information about the template scope.

Operations

Registrations

Manage template registrations.

Operations

Manage Templates

Manage Templates.

Operations

Retrieve All Templates in Scope

Request

Returns all templates within the given template scope.

Path
templateScopeIdstring(uuid)required

Template scope ID

Query
sizeany

Page size

pageany

The page to retrieve (starts at zero).

sortany

The field name to sort, comma separated from the sort order (asc or desc). Sortable fields are: id, nameLocalizationKey, userProvidedName, messageTemplate, and extraFieldOneTemplate

No request payload

Responses

The list of templates within the template scope.

Body
pagingobject(Page Information)

The paging information for this response.

contentArray of objects(Template)

The content list of the data.

_linksobject(Links)
Response
{ "paging": { "totalCount": 0, "page": 0, "pageSize": 0, "pageCount": 0 }, "content": [ {} ], "_links": { "property1": {}, "property2": {} } }

Retrieve Template

Request

Returns the template specified by the given id, which can be either a registration id or template id.

Path
templateScopeIdstring(uuid)required

Template Scope ID

genericTemplateIdstringrequired

Template or Registration ID

No request payload

Responses

The template

Body
idstringread-only

The template ID. If the template is retrieved with a registration ID this will still be the template ID.

nameLocalizationKeystringread-only

A key which can be used to reference the name of the template.

userProvidedNamestringnon-emptyrequired

A user provided name for the template. If available this should be used instead of the name localization key.

messageTemplatestringrequired

The template.

extraFieldOneTemplatestring

An extra template field which can be used in conjunction with the template; used for the subject in email templates.

editablebooleanread-only

True if the template was user generated and therefore can be edited.

_linksobject(Links)
Response
{ "id": "string", "nameLocalizationKey": "string", "userProvidedName": "string", "messageTemplate": "string", "extraFieldOneTemplate": "string", "editable": true, "_links": { "property1": {}, "property2": {} } }