Intervals API Resource:

personcontact

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

For accessing and updating contact information about people. This includes phone numbers, email addresses, physical addresses, websites, etc.

Collection

Allowed HTTP Methods
MethodGroup Access
GETAdministrator, Manager, Resource, Executive
Allowed Filters
Filter NameRequired?ExpectsDefaultDescription
personid yes integer
contacttypeid no integer
contactdescriptorid no integer

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

Examples

To filter the list based on certain parameters:

GET /personcontact/?personid={value}

Note: You can string together multiple filters.

Member

Allowed HTTP Methods
MethodGroup Access
GETAdministrator, Manager, Resource, Executive
DELETEAdministrator, Manager, Resource, Executive
POSTAdministrator, Manager, Resource, Executive
PUTAdministrator, Manager, Resource, Executive
Settable Fields for PUT and POST Requests
Field NameRequired?ExpectsDefaultDescription
personid yes integer The ID of the person to whom this contact information applies. Keep in mind only administrators may edit other people's contact information.
value yes string
contacttypeid yes integer
contactdescriptorid yes 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 NameNullableDescription
id no Unique identifier for the person contact
personid no ID of the person this contact belongs to
contact_type_id no ID of the contact type (see `/contacttype/`)
contact_descriptor_id no ID of the contact descriptor (see `/contactdescriptor/`)
value no The stored value (email address, phone number, URL, etc.)
contact_type no Contact type key or label (e.g. email, phone)
contact_descriptor no Descriptor label within the type (e.g. Work, Home, Other)

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

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

To delete a particular member resource:

DELETE /personcontact/{id}/

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

To create a new member resource:

POST /personcontact/
{
    "personid": value,
    "value": value,
    "contacttypeid": value,
    "contactdescriptorid": 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 /personcontact/{id}/
{
    "personid": value,
    "value": value
}

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

Start tracking time today

Join 5,000+ companies spending their time wisely with Intervals.

Try Intervals free