Showing results for 
Search instead for 
Did you mean: 

Virtual SmartZone API : How should serviceTicket be used?

New Contributor
I'm currently building a service to communicate with a Virtual SmartZone. On startup, the service calls the v7_0/serviceTicket route and receives a service ticket back, which is used as a URI parameter for all other requests:

 However, the docs do not state how long this service ticket is active for, and how old service tickets should be cleaned up. I have tried the DELETE method for this route and it appears to not work. After running DELETE on /serviceTicket with the ticket id, I still am able to use that ticket id. There is also no way to get a list of old service tickets so that they could be cleaned up.

 I am worried about creating too many service tickets, and eventually slowing down or crashing the server. Is this is a valid concern? Should I just create one serviceTicket and then use that as a constant value instead of creating a new one each time? 

Esteemed Contributor II
I don't know anyone with experience using "v7_0/serviceTicket" application/tool that you are asking about.
This doesn't seem to be related to the SmartZone controller.
Does the company that supports "v7_0/serviceTicket" provide answer in their docs, or have contact you can ask?

New Contributor
Hi Nick,

Same issue here. Not sure how this works.

Michael, "v7_0/serviceTicket" refers to the route required to create a serviceTicket through the Ruckus SmartZone controller API as per the documentation. link below:


New Contributor II
Does anyone have any information on this?

On I receive an 500 (internal error) response when calling the DELETE method on the serviceTicket endpoint, and the serviceTicket continues to work for other requests.

The URI of my request is 'https://{ruckuscontrollerfqdn}:8443/wsg/api/public/v8_0/serviceTicket?serviceTicket={myserviceTicket}'

The same error occurs if I use v7_0

New Contributor
I opened a ticket up for this months ago and still haven't gotten an answer on how service ticket should be used. I ended up going the route of creating a new service ticket for every request. The DELETE method doesn't appear to work.

I still would appreciate an answer from the software developers at Ruckus on how they designed service ticket.