Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

titleStringThe title for the expense. For example, "Flights to Hawaii".
against_idIntegerThe id of the object the task exists against. This must point to a valid object.
against_typeString"issue" or "job". The type of object the task exists against. If you supply an invalid linked object type, you will get an invalid request error with description like "Engagement must be an issue or job".
unit_costFloatThe cost per unit of the expense. For example, "10.50". If you have a quantity of "3", you would then have a total expense cost of "31.50"
quantityIntegerThe number of units included in the expense. For example, "3". If you have a unit cost of "10.50", you would then have a total expense cost of "31.50"
type_idIntegerThe id of the expense type you wish the new expense to be a part of.
date_incurredISO8601 Date StringFor example, "2016-01-20T11:13:04+11:00". This will default to now.
billableBit1 is billable and 0 is non-billable. This defaults to 0, for non-billable.
reimbursableBit1 is reimbursable and 0 is not reimbursable. This defaults to 0, for not reimbursable.
_fieldspartial stringAllows you to specify optional fields and linked objects to include in the response. See get expense for more information.

...