Ticket/List

List and search for one or multiple support tickets.

Parameters
Parameter Type Required Description
ticket_id string optional Provide a 'ticket_id' to list a specific ticket
friendly_ticket_id string optional Provide a 'friendly_ticket_id' to list a specific ticket.
direction string optional List tickets based on their direction by providing a direction.
working_status string optional Supply 'working_status' to list tickets of a specific working status.
customer_account_id string optional Supply a 'customer_account_id' to list tickets connected to a specific customer account.
subscription_id string optional Supply a 'subscription_id' to list tickets connected to a specific subscription.
limit string optional Limit the amount of results returned. Valid options are between 1 and 300. Default is 300.
order string optional Order results by descending 'desc' or ascending 'asc'.
offset string optional Offset the results returned. An 'offset' of 10 would skip the first ten results.
GET https://api.recurringstack.com/{format}/Ticket/List
//key,user_key,brand_id,response_format (xml or json),return (clean = return object, leave blank to return raw)
$rstack = new recurringstack('','','','xml','clean'); 

$params = array('ticket_id' => "",'friendly_ticket_id' => "",'direction' => "",'working_status' => "",'customer_account_id' => "",'subscription_id' => "",'limit' => "",'order' => "",'offset' => "");
try { $response = $rstack->request('Ticket/List','GET',$params); } catch(Exception $e) { $error =  $e->getMessage(); echo "Error: $error"; }
print_r($response);
Response

Ticket/Create

Create a new ticket or create a new message on an existing ticket.

Support tickets have a unique 'ticket_id' and 'friendly_ticket_id'. The 'friendly_ticket_id' is shorter and more customer friendly. Either ID can be used to retreive the ticket details (Ticket/List).

Only the 'ticket_id' can be used to update, delete, or create a new message on a ticket.
Ticket 'direction' is only supplied when posting the first message on a ticket (ie. creating a new ticket).

INTERNAL tickets are not viewable by customers.
EXTERNAL tickets are considered viewable by customers, must have a linked 'customer_account_id'..
EXTERNAL-CUSTOMER tickets are considered opened by an existing or potential customer. When 'customer_account_id' is provided the ticket is considered opened by the customer. When 'guest_email' is supplied the ticket is considered opened by a guest or potential customer.

Parameters
Parameter Type Required Description
type string required NEW (create a new ticket) or REPLY (create a message on an existing ticket)
ticket_id string optional Required for REPLY Provide a 'ticket_id' of an existing ticket to create a new REPLY.
message string required The contents of your message.
attachments string optional A comma seperated list of images or files you wish to attach to the message. Must be the full url path to an image.
subject string optional New Tickets Only The subect of the ticket. Only required when creating a NEW ticket.
direction string optional New Tickets Only Options are INTERNAL; EXTERNAL; or EXTERNAL-CUSTOMER.
department string optional New Tickets Only Specify the department for the new ticket. There are no optional values and any text value is acceptable (ex. SALES or TECH SUPPORT).
customer_account_id string optional Assosiate a new ticket with a customer account by providing a 'customer_account_id'. Also provide the 'customer_account_id' in addition to the 'customer_user_id' when posting a reply as a customer
customer_user_id string optional If the message is being posted by a customer account user provide that users 'user_id' as 'customer_user_id'. Required when 'customer_account_number' is provided.
subscription_id string optional New Tickets Only Associate the ticket with an existing subscription. 'customer_account_id' must also be supplied.
guest_email string optional If the message is being created by a guest (potential customer) provide their email address. Ticket 'type' must be 'EXTERNAL-CUSTOMER'.
POST https://api.recurringstack.com/{format}/Ticket/Create
//key,user_key,brand_id,response_format (xml or json),return (clean = return object, leave blank to return raw)
$rstack = new recurringstack('','','','xml','clean'); 

$params = array('type' => "",'ticket_id' => "",'message' => "",'attachments' => "",'subject' => "",'direction' => "",'department' => "",'customer_account_id' => "",'customer_user_id' => "",'subscription_id' => "",'guest_email' => "");
try { $response = $rstack->request('Ticket/Create','POST',$params); } catch(Exception $e) { $error =  $e->getMessage(); echo "Error: $error"; }
print_r($response);
Response

Ticket/Update

Update an existing ticket, including the ticket status.

Unlike all other update services, the 'Ticket/Update' service will only update paramatets you pass to it, this allows you to leave certain parameters empty and only update the ones supplied. For example, if you provide the 'subject' paramenter the subject will be updated, otherwise it will remain the same.

Parameters
Parameter Type Required Description
ticket_id string required The 'ticket_id' you wish to update.
subject string optional The subject of the ticket.
working_status string optional The current working status of the ticket. Valid options are OPEN; ANSWERED; WORKING; ON HOLD; or CLOSED.
department string optional Specify the department for the new ticket. There are no optional values and any text value is acceptable (ex. SALES or TECH SUPPORT).
customer_account_id string optional Update the associated customer account by providing a 'customer_account_id'.
subscription_id string optional Update the associated subscription. 'customer_account_id' must also be supplied.
PATCH https://api.recurringstack.com/{format}/Ticket/Update
//key,user_key,brand_id,response_format (xml or json),return (clean = return object, leave blank to return raw)
$rstack = new recurringstack('','','','xml','clean'); 

$params = array('ticket_id' => "",'subject' => "",'working_status' => "",'department' => "",'customer_account_id' => "",'subscription_id' => "");
try { $response = $rstack->request('Ticket/Update','PATCH',$params); } catch(Exception $e) { $error =  $e->getMessage(); echo "Error: $error"; }
print_r($response);
Response

Ticket/Merge

Merge one ticket with another ticket. Messages from both tickets will be maintained while the subject of the original ticket (ticket_id) will be maintained.

Once two tickets are merged the action cannot be reversed. Characterstics from the original ticket ('ticket_id') will persist, including subject, direction, and department.
If either ticket has a 'customer_account_id' or 'subscription_id' they must match for the merge to be successful.

Parameters
Parameter Type Required Description
ticket_id string required The original 'ticket_id' you wish to merge with the 'merge_ticket_id'.
merge_ticket_id string required The 'ticket_id' of the ticket to merge with. This ticket will no longer exist after the merge.
PATCH https://api.recurringstack.com/{format}/Ticket/Merge
//key,user_key,brand_id,response_format (xml or json),return (clean = return object, leave blank to return raw)
$rstack = new recurringstack('','','','xml','clean'); 

$params = array('ticket_id' => "",'merge_ticket_id' => "");
try { $response = $rstack->request('Ticket/Merge','PATCH',$params); } catch(Exception $e) { $error =  $e->getMessage(); echo "Error: $error"; }
print_r($response);
Response

Ticket/Delete

Delete a support ticket.

Parameters
Parameter Type Required Description
ticket_id string required The 'ticket_id' of the ticket you wish to delete.
DELETE https://api.recurringstack.com/{format}/Ticket/Delete
//key,user_key,brand_id,response_format (xml or json),return (clean = return object, leave blank to return raw)
$rstack = new recurringstack('','','','xml','clean'); 

$params = array('ticket_id' => "");
try { $response = $rstack->request('Ticket/Delete','DELETE',$params); } catch(Exception $e) { $error =  $e->getMessage(); echo "Error: $error"; }
print_r($response);
Response

Your content here

Lorem ipsum dolor sit amet consectetur adipisicing elit. Qui, natus temporibus voluptate corporis possimus ab aut cumque.

Homepage

Quick Tips

You may remove all ID or Class names which contain _dm-, they are only used for demonstration.


Boxed Layout

Fluid Layout Remove the .boxed-layout and .centered-layout classes from the body.
Centered Layout Add a class .centered-layout to the body.
Boxed Layout Add a class .boxed-layout to the body.
Boxed Layout with background image

Add background image to the body.

<body class="boxed-layout" style='background-image: url("path_to_img/image.jpg");'>
    ..
    ..
</body>

Or it could be in your own class.

.bg-img {
background-image: url("path_to_img/image.jpg");
}
<body class="boxed-layout bg-img">
    ..
    ..
</body>

Color Schemes

Replace the current Bootstrap CSS and Nifty CSS path with the new path of the CSS color schemes you wish to use.

This is where you can change the color scheme of your app / website.

<head>
    ...
    <title>My Project</title>
    ...

    <!-- STYLESHEETS -->
    <!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~--- -->

    <!-- Bootstrap CSS [ REQUIRED ] -->
    <link rel="stylesheet" href="documentation/assets/css/color-schemes/SELECTED-SCEHEMS/bootstrap.min.css">

    <!-- Nifty CSS [ REQUIRED ] -->
    <link rel="stylesheet" href="documentation/assets/css/color-schemes/SELECTED-SCEHEMS/nifty.min.css">

</head>

Header

Sticky header Add a class .hd--sticky to the #root.
Expanded header Add a class .hd--expanded to the #root.
Expanded header with overlapping content. Add a class .overlapping to the #content > .content__header.
Disable rounded header. Add a class .rounded-0 to the #content > .content__header.

Animations

Add the following class to the body to change the animation transition.

Transition function name Class name
In Quart .in-quart
Out Quart .out-quart
In Back .in-back
Out Back .out-back
In Out Back .in-out-back
easeInOutBack .easeInOutBack
steps .steps
jumping .jumping
rubber .rubber
RecurringStack Documentation
RecurringStack Docs
Sign In

Background Images

Add an image to replace the solid background color
Layouts
Layouts
Transitions
Header
Additional Offcanvas New in BS v.5.0

Select the offcanvas placement.

Sidebars
Navigation
Right sidebar
Color Schemes
Light Completely bright color themes.
Dark Completely dark color themes.
Expanded Header
Fair Header
Full Header
Primary Nav
Brand
Tall Header New in v3.0
Scrollbars

Hides native scrollbars and creates custom styleable overlay scrollbars.

Offcanvas Header
Content Here

Lorem ipsum dolor sit amet, consectetur adipisicing elit. Sapiente eos nihil earum aliquam quod in dolor, aspernatur obcaecati et at. Dicta, ipsum aut, fugit nam dolore porro non est totam sapiente animi recusandae obcaecati dolorum, rem ullam cumque. Illum quidem reiciendis autem neque excepturi odit est accusantium, facilis provident molestias, dicta obcaecati itaque ducimus fuga iure in distinctio voluptate nesciunt dignissimos rem error a. Expedita officiis nam dolore dolores ea. Soluta repellendus delectus culpa quo. Ea tenetur impedit error quod exercitationem ut ad provident quisquam omnis! Nostrum quasi ex delectus vero, facilis aut recusandae deleniti beatae. Qui velit commodi inventore.