Skip to content

Creating a Ticket

Tickets can be created in Hausing via the REST API. Below is a step-by-step guide.

  • 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

Find the building ID to create the ticket for via the Buildings API.

Find the room ID to create the ticket for via the Buildings API.

Compose the ticket request using data from the buildings and rooms requests. See the Ticketing API reference for full request documentation.

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.

Adding files to a ticket is a multi-step process. For each file:

  1. Acquire upload URL — see the Files API reference for the upload URL endpoint. Files are uploaded to AWS S3.

  2. Upload the file — use the signed upload URL returned by step 1. Refer to the Uploading a File guide.

  3. Register the file — send a request to the Files API with the following data:

    • entityExternalId — ticket ID returned by the create ticket request
    • entityNameTicket
    • apiNameticketing-api
    • fileNamefileName returned by the upload URL request
    • originalFileName — refer to API documentation
    • visibilities — refer to API documentation
    • creatorContext — a map with key email and value set to the watcher email