InvoicingList payment terms

List payment terms

Lists the account's payment terms (due-date rule, interest, reminder fee).

Returns every payment term that is visible in the system (hidden ones are excluded; inactive ones are included), ordered by ID. Use it to pick PaymentTermID for a customer.

Use it to:

  • Pick PaymentTermID for POST /v1/customer/create
  • Compute an invoice's due date client-side (CreditTerm + DaysOfCredit)

Behaviour:

  • Idempotent.
  • Safe to retry.
  • Changes are visible to the next read immediately.

Next: POST /v1/customer/create

curl -X GET "https://app3.timelog.com/your-account/api/v1/payment-term?$page=1&$pagesize=10" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_TOKEN"
{
  "Properties": {
    "TotalRecord": "1",
    "TotalPage": "1",
    "PageNumber": "1"
  },
  "Entities": [
    {
      "Properties": {
        "ID": 2,
        "Name": "Net 30 days",
        "TermMessage": "Payment terms: 30 days net 
If you miss a due date interests pursuant to applicable laws are added.",
        "CreditTerm": "NET",
        "DaysOfCredit": 30,
        "InterestRate": 3,
        "InterestPeriod": "FourteenDays",
        "ReminderFee": 100,
        "IsDefaultTerm": true,
        "IsActive": true,
        "CurrencyID": 9,
        "PaymentTermGuid": "6b218693-3f85-4430-87a8-7cdb930b126a"
      }
    }
  ],
  "Links": [
    {
      "Href": "https://app{server-number}.timelog.com/{account}/api/v1/payment-term",
      "Rel": "self"
    }
  ]
}
GET
/v1/payment-term
GET
Base URLstring

Target server for requests. Edit to use your own host.

Bearer Token
Bearer Tokenstring
Required

OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp). The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user. > Not yet documented: how to obtain a token. > Not yet documented: token lifetime.

OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp). The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user. > Not yet documented: how to obtain a token. > Not yet documented: token lifetime.
query
$pageinteger

Page number (1-based).

query
$pagesizeinteger

Page size. No maximum enforced in the API layer.

Request Preview
Response

Response will appear here after sending the request

Authentication

header
Authorizationstring
Required

Bearer token. OAuth 2.0 bearer token, sent as Authorization: Bearer <token>. JWT and reference tokens are both accepted. The token must carry the required scope (default tlp).

The token's sub claim is the acting user. A token WITHOUT sub (client-credentials) acts as the system service user. If the sub user cannot log in (inactive, locked, deleted), the request is rejected with 401 — it is no longer let through without a user.

Not yet documented: how to obtain a token.

Not yet documented: token lifetime.

Query Parameters

$pageinteger

Page number (1-based).

$pagesizeinteger

Page size. No maximum enforced in the API layer.

Responses

Propertiesobject

Paging values. They are returned as STRINGS, for example "TotalRecord": "12".

Entitiesarray

Omitted (not []) when the list is empty.

Linksarray