MagicDoorAPI
SupportOpen MagicDoor
Association violations

Update an association violation

Replaces the editable details of a violation: its dates, its fine amount, its title and its description. Every field in the body is written, so send the current value for anything you are not changing.

PUT
https://api.portal.magicdoor.com/company-app/associations/violations/{violationId}

Authorization

Authorizationstringrequired
Bearer token — Send your API token in the Authorization header as Bearer <token>. Requests without a valid token are rejected with 401 Unauthorized.

Path parameters

violationIdstringrequired

The association violation to act on. A Snowflake id sent as a decimal string.

example: 1830472847398407007

Body

application/json

The violation's property, unit, lease, association vendor and status cannot be changed here. Use the status endpoint for the status.

violationReceivedDatestring · daterequired

The day the notice reached you.

violationDatestring · daterequired

The day the violation happened.

fixByDatestring · date

The deadline the association gave. Leave it out to clear it.

associationFinenumberrequired

The fine the association charges, for example 250.00.

titlestringrequired

Short title.

descriptionstringrequired

What the association says is wrong.

Response

200 · The violation after the change.

idstring

The violation. A Snowflake id sent as a decimal string.

portfolioIdstring

The portfolio the violation was raised against.

propertyIdstring

The property the violation was raised against.

unitIdstring

The unit the violation was raised against. Absent when the violation is property-wide.

leaseIdstring

The lease the violation was raised against. Absent when no lease is involved.

statusenum<string>

Where the violation sits in its workflow.

receivedinProgressresolved
hoaVendorIdstring

The vendor record for the homeowners association that issued the violation.

referencestring

The association's own reference for the violation. Generated automatically when the caller did not supply one.

violationReceivedDatestring · date

The day the association's notice reached the property manager.

violationDatestring · date

The day the violation itself happened.

fixByDatestring · date

The deadline the association gave for putting it right. Absent when no deadline was given.

associationFinenumber

The fine the association charges, for example 250.00. Absent when no fine was recorded.

titlestring

Short title. Written by an AI summary of the description when the caller did not supply one.

descriptionstring

What the association says is wrong.

notificationSentAtstring · date-time

When a notice was last sent to the lease or the owners, in the company's timezone. Absent while no notice has been sent.

filesobject[]

Files attached to the violation, such as the association's own notice.

propertyFineBillobject

The vendor bill raised against the property for the association's fine. Absent until the fine is charged.

leaseFineBillobject

The lease charge raised when the fine was passed on to the tenant. Absent when the fine was not passed on.

portfolioobject

The portfolio the violation belongs to.

propertyobject

The property the violation was raised against.

unitobject

The unit the violation was raised against. Absent when the violation is property-wide.

leaseobject

The lease the violation was raised against. Absent when no lease is involved.

workOrdersobject[]

Work orders raised from this violation.

leaseBillsobject[]

Extra lease charges added against this violation, beyond the fine itself.

ownersobject[]

Owners of the property, as used when sending an owner notice.

workOrderVendorsobject[]

Vendors assigned to the work orders above.

401 · The access token is missing, expired, or not valid for this company.

404 · No association violation with that id exists in the caller's company.

Changing associationFine after the fine has already been charged does not change the bill that was raised. That bill has to be corrected on its own.