Intervals API Resource:

payment

The base URL for this resource is located at
https://api.myintervals.com/payment/

Collection

Allowed HTTP Methods
Method	Group Access
GET	Administrator, Manager, Executive

Allowed Filters
Filter Name	Required?	Expects	Default	Description
clientid	no	integer		Limits the list to payments belonging to the client with the ID passed.
projectid	no	integer		Limits the list to payments belonging to the client with the ID passed.
personid	no	integer¹		Limits the list to payments posted by the persons with the ID passed.
date	no	date		Limits the list to payments having the date passed.
typeid	no	integer		Limits the list to payments having the payment type of the ID passed. For more information, see the paymenttype resource.
invoiceid	no	integer		Limits the list to payments belonging to the invoice with the ID passed.
sortfield	no	string		Sort the list by any of the following fields: id, projectid, date, amount, typeid, reference, note, invoiceid, type, project, and client.
sortdir	no	string		Sets the sort direction of the returned list. Must be either "ASC" or "DESC".
offset	no	integer		Return payments starting from the nth payment.
limit	no	integer	10	Sets a limit to the amount of invoices returned in the response.

¹ Indicates that multiple values are allowed, in CSV format (e.g. "3,5,11,19").
² This field accepts HTML, but certain HTML elements may be stripped out.

Examples

To retrieve the entire list of this resource:

GET /payment/

To filter the list based on certain parameters:

GET /payment/?date={value}

Note: You can string together multiple filters.

Member

Allowed HTTP Methods
Method	Group Access
GET	Administrator, Manager, Executive
DELETE	Administrator
POST	Administrator, Manager
PUT	Administrator, Manager

Settable Fields for PUT and POST Requests
Field Name	Required?	Expects	Default	Description
projectid	yes	integer
date	yes	date
amount	yes	double
typeid	yes	integer
reference	no	string (35)		If the payment type is of type Other, a descriptor for that can be stored here.
note	no	string (255)		A description for the payment.
invoiceid	no	integer

string (xxx) indicates a string with a maximum length of xxx characters.

Response Fields

The fields below are returned in GET responses. Boolean values are "t" / "f" strings. Numeric IDs and floats are returned as strings. Nullable fields may be JSON null.

Response Fields
Field Name	Nullable	Description
id	no	Unique identifier for the payment
projectid	no	ID of the associated project
date	no	Payment date (YYYY-MM-DD)
amount	no	Payment amount (May be returned as a string in JSON)
typeid	no	ID of the payment type
reference	yes	Payment reference (check number, transaction id, etc.)
note	yes	Payment description or notes
invoiceid	yes	ID of the invoice this payment is applied to
personid	no	ID of the person who recorded the payment (Not shown to Executive users)
type	no	Payment type name (e.g. Credit Card)
project	no	Name of the associated project
person	no	Full name of the person who recorded the payment (Not shown to Executive users)
invoice	yes	Human-readable invoice identifier shown in the app (e.g. invoice number)
client	yes	Name of the associated client (empty when none)
clientid	yes	ID of the associated client (empty or omitted when none)

Sample response object. Non-null values are strings in JSON (including IDs, numeric fields, and booleans as "t" / "f"). Nullable fields may be JSON null when absent.

{
    "id": "123456",
    "projectid": "123456",
    "date": "2026-01-15",
    "amount": "1.5",
    "typeid": "123456",
    "reference": "REF-001",
    "note": "Note text",
    "invoiceid": null,
    "personid": "123456",
    "type": "Type Name",
    "project": "Project Name",
    "person": "First Last",
    "invoice": "string value",
    "client": null,
    "clientid": null
}

When retrieving a collection (GET /payment/), the response envelope includes: personid (authenticated user's ID), status ("OK"), code (200), listcount (total matching records before limit/offset), and payment (array of result objects). Defaults, no cap on limit, and how to paginate using listcount are described in the API Introduction (Pagination).

Examples

To retrieve one member resource:

GET /payment/{id}/

Assuming no errors, the server will respond with 200 OK and the object requested.

To delete a particular member resource:

DELETE /payment/{id}/

Assuming no errors, the server will respond with 200 OK.

To create a new member resource:

POST /payment/

{
    "projectid": value,
    "date": value,
    "amount": value,
    "typeid": value
}

Assuming no errors, the server will respond with 201 Created and the newly-created element. This will allow you to get the id of the item you just created and verify the field values. Note: Only required fields were listed here. The entire list of possible fields is above.

To update a member resource:

PUT /payment/{id}/

{
    "date": value,
    "reference": value
}

Assuming no errors, the server will respond with 202 Accepted and the entire element. This will allow you to verify the field values.

Documentation

Resources

API Support

Looking for help?
Contact our support team.

OpenAPI

OpenAPI JSON spec (public)

Swagger UI on SwaggerHub

Start tracking time today

Connect Intervals to the tools and workflows your team already uses.

Try Intervals free