Invoice / Due Date Type

(API Version v3)

Determines what the invoice "due-date" is based on. It let's the user define if the invoice due-date is based on when the invoice is rendered or when the account bill day. The Due date will also be affected by any dunning rules assigned.

What can you do with InvoiceDueDateType?

• GET api/v3/Invoice/DueDateType/
  
  Retrieve all of the InvoiceDueDateType objects.
  
  
• GET api/v3/Invoice/DueDateType/Paged
  
  Retrieve all of the InvoiceDueDateType objects in a paged fashion.
  
  
• GET api/v3/Invoice/DueDateType/{id}
  
  Retrieve an instance of the InvoiceDueDateType object by its ID.
  
  

Properties

Update Request Filters

When updating an object you use the update request header with the list of properties to update. Then you need only supply the new values in the body of your request. Please note, this header can only be used with PUT or PATCH requests.

Field List:

• name

End Points

GET api/v3/Invoice/DueDateType/

HTTP/1.1 200 OK
{
    "trackingId": "d2ae5304-2355-44eb-a328-272f02935f8b",
    "totalCount": 1,
    "items": [
        {
            "identity": 1,
            "name": "Sample Text Data"
        }
    ]
}

GET api/v3/Invoice/DueDateType/Paged

HTTP/1.1 200 OK
{
    "trackingId": "d2ae5304-2355-44eb-a328-272f02935f8b",
    "pagination": {
        "pageNumber": 1,
        "pageSize": 20,
        "excludeTotalCount": false
    },
    "pagedResults": {
        "totalCount": 1,
        "items": [
            {
                "identity": 1,
                "name": "Sample Text Data"
            }
        ]
    }
}

GET api/v3/Invoice/DueDateType/{id}

HTTP/1.1 200 OK
{
    "trackingId": "d2ae5304-2355-44eb-a328-272f02935f8b",
    "instance": {
        "identity": 1,
        "name": "Sample Text Data"
    }
}