Intervals API Resource:

request

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

The request resource is used to manage work requests.

Permissions for work requests are not entirely straightforward, so here are some general rules:

1. Administrators can view, change or delete any work request.
2. Managers may view, change or delete any work request to which they have project access. However, they cannot change the person with whom the work request is associated once it has been set.
3. Resource and executive users may view any work request to which they have project access. However, they cannot change or delete the work request unless they are the person with whom the work request is associated.
4. Work requests can have no project. In these cases, view access by managers, resources and executives is allowed if they are included in the mail queue notification list or if they are the person with whom the work request is associated. Managers may edit or delete these work requests, but resource and executive users can only do so if they are the person with whom the work request is associated.

Collection

¹ 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:

To filter the list based on certain parameters:

Note: You can string together multiple filters.

Member

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

Response Fields

{
    "id": "123456",
    "personid": "123456",
    "title": "Example Title",
    "date": "2026-01-15 14:30:00",
    "description": "<p>Example text</p>",
    "projectid": null,
    "priorityid": "123456",
    "datedue": null,
    "localid": "123456",
    "headers": "string value",
    "clientid": null,
    "client": null,
    "person": "First Last",
    "person_localid": null,
    "email": "user@example.com",
    "project": "Project Name",
    "projectactive": "t",
    "priority": "3",
    "projectlocalid": null,
    "personvisible": "t"
}

When retrieving a collection (GET /request/), the response envelope includes: personid (authenticated user's ID), status ("OK"), code (200), listcount (total matching records before limit/offset), and request (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:

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

To delete a particular member resource:

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

To create a new member resource:

{
    "personid": value,
    "priorityid": value,
    "title": 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:

{
    "projectid": value,
    "title": value
}

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