website logo
⌘K
Getting Started
What is TIDY?
Getting Started: Rental Properties
Getting Started: Employer Benefits
Getting Started: Residential Homes
Getting Started: Offices
Dashboard
TIDY AI
Acceptance Probability
Teams & Users
Users
Teams
Properties/Addresses
Access Instructions
Jobs
Add or Request a Job
View, Edit, or Cancel Jobs
Setting Backup Times
Job Links
Job Reviews or Feedback
Resolving Pro Cancellations
Account Settings
Messages
Notifications
Plans
Access Control / Smartlocks
My Pros
Booking Different Type Of Services With Your Pros
Private Cleaning Payment
Defining your Job Request Strategy
To-Do Lists
Video Introductions
To-Do List Links
To-Dos
Do-Nots
Remote Inspections
Custom Fields
Laundry or Linens
Supply Preferences
Integrations
Automatic Booking
Billing, Pricing, & Payments
Billing History
Sending Payments
Bills & Payment Methods
Team Billing
View & Edit Prices
Viewing Billing History
Tips
Refunds
Rebate Program
Tax Reporting for Payments to Pros
Compliance, Ratings, Safety, Insurance, & Protection
Insurance or Custom Requirements
Certifications & Ratings
Satisfaction Guarantee, Disputes, & Protection
Damage Claims
Property Maps
Maintenance
Inventory Tracking
Inspections
Smart Thermostats
Issue Tracking
Automatic Translation
Other Questions
TIDY Concierge
Reports
Accounting
Developers
API Introduction
Authentication
Changelog
Errors
API Reference
Webhooks
Best Practices
Docs powered by archbee 

Create an Issue

2min
POST

Create an Issue.

To create an Issue you must enter an address_id, a description and type.

AUTHENTICATION
Authorization
string
Bearer
BODY PARAMETERS
body
object
address_id
integer
*
The ID of the `Address` that the `Issue` occured
description
string
*
The description of what the `Issue` is
type
string<damage | low_inventory>
*
The type of `Issue` that was reported. Either `damage` or `low_inventory`
RESPONSES
200
OK
Issue
## About Issues Issues can be reported about an `Address`. Issues are things that happen at the property that needs follow up from you. They can be reported either by the `Pro` on the `Job` or by someone on your account. ## More details about Issues | Attribute | Description | | ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | id | The ID of the `Issue` | | address_id | The ID of the `Address` that the `Issue` occured | | description | The description of what the `Issue` is | | reporter_type | Who reported the `Issue`.
**customer** - The `Issue` was created by the customer account.
**pro** - The `Issue` was created by the `Pro` on a `Job`. | | status | Status of the `Issue`.
**open** - The `Issue` is open and needs resolution.
**resolved** - The `Issue` is resolved, no further action needed. | | type | The type of `Issue` that was reported.
**damage** - The `Issue` is damage related.
**low_inventory** - The `Issue` is related to low inventory.` | | created_at | The date and time the `Issue` was created. UTC and ISO formatted. | |
object
string
*
id
integer
*
The ID of the `Issue`
address_id
integer
*
The ID of the `Address` that the `Issue` occured
description
string
*
The description of what the `Issue` is
reporter_type
string< | pro | customer>
*
Who reported the `Issue`.
**customer** - The `Issue` was created by the customer account.
**pro** - The `Issue` was created by the `Pro` on a `Job`.
status
string<open | resolved>
*
Status of the `Issue`.
**open** - The `Issue` is open and needs resolution.
**resolved** - The `Issue` is resolved, no further action needed.
type
string<damage | low_inventory>
*
The type of `Issue` that was reported. Either `damage` or `low_inventory`
created_at
string
*
The date and time the `Issue` was created. UTC and ISO formatted.




Updated 26 Apr 2023
Did this page help you?
Yes
No
PREVIOUS
List all Issues
NEXT
Retrieve an Issue
Docs powered by archbee