Creating a Ticket
Tickets can be created in Hausing via the REST API. Below is a step-by-step guide.
Prerequisites
Section titled “Prerequisites”- Client ID and Client Secret — please contact support to obtain these
- Company ID — provided with Client ID and Client Secret by Hausing Support
- Basic knowledge of APIs
- See Authentication and Error Handling
Process
Section titled “Process”Step 1. Get all buildings (optional)
Section titled “Step 1. Get all buildings (optional)”Find the building ID to create the ticket for via the Buildings API.
Step 2. Get all rooms (optional)
Section titled “Step 2. Get all rooms (optional)”Find the room ID to create the ticket for via the Buildings API.
Step 3. Create ticket
Section titled “Step 3. Create ticket”Compose the ticket request using data from the buildings and rooms requests. See the Ticketing API reference for full request documentation.
Step 4. Add ticket watcher
Section titled “Step 4. Add ticket watcher”A ticket watcher is an email address marked as the ticket creator who will be notified of ticket activities. See the Ticketing API reference for the add watcher endpoint.
Step 5. Add files (optional)
Section titled “Step 5. Add files (optional)”Adding files to a ticket is a multi-step process. For each file:
-
Acquire upload URL — see the Files API reference for the upload URL endpoint. Files are uploaded to AWS S3.
-
Upload the file — use the signed upload URL returned by step 1. Refer to the Uploading a File guide.
-
Register the file — send a request to the Files API with the following data:
entityExternalId— ticket ID returned by the create ticket requestentityName—TicketapiName—ticketing-apifileName—fileNamereturned by the upload URL requestoriginalFileName— refer to API documentationvisibilities— refer to API documentationcreatorContext— a map with keyemailand value set to the watcher email