Skip to main content
URL parameters let you control SuperOffice Service using simple HTTP commands. These commands are similar to a REST API. However, they return a full HTML user interface, not JSON or XML as REST would return. For example, this URL will open a list of tickets for the current user: http://server/custsvc/ticket.exe?action=listTickets

URL structure

The 1st component is the site address, including customer ID and the CS sub-directory. For example: https://sod.superoffice.com/CustXXXXX/CS/ The 2nd component is the endpoint, specifying which program to run:
  • blogic.exe
  • customer.exe
  • ticket.exe
  • document.exe
  • rms.exe
  • stat.exe
3rd and last is the query string, specifying an action and possibly a list of parameters. Multiple parameters are separated with an ampersand &. For example, action=listTickets or action=doScript&id=123.

bLogic

You must set exactly 1 parameter for blogic actions. For scripts, use either id or includeId. For screens, use id or idString. Don’t supply both!

Customer

Global parameters common to all customer actions:
  • custSessionKey
  • noCookies
  • templateFolder
  • withFrame=1 or withFrame=0
The key must be the same as set in the script!

Ticket

You must set exactly 1 parameter for screen definitions. Use either id or idString - don’t supply both!

Document

Rms

Stat