Couple Relationship Change History

Description

The Couple Relationship Change History resource provides a list of changes for a couple relationship. Each entry in the change history provides details about what was changed, who performed the change, and an explanation of why the change was made if the reason was provided by the user.

Data Formats

If you make a GET request, specify the data format using the Accept header.

If you POST something, specify the media type using the Content-Type header.

Parameters

Name Type Description
Authorization header The authorization carrying the OAuth 2.0 access token. See OAuth 2.0 Bearer Tokens.
crid path The id of the couple relationship used to obtain the change history.
count query The number of change history entries to include in this page.
from query The id of the last change that was retrieved. The request will return the changes following this id.
access_token query The ID of the OAuth 2 access token used for identification and authorization of the user (and agent) making the request.

Operations

HEAD - Read the headers for the couple relationship history.

Status Codes
200 Upon a successful read.
204 Upon a successful read with an empty change history.

GET - Read the couple relationship history.

Status Codes
200 Upon a successful read.
204 Upon a successful read with an empty change history.
429 If the request was throttled.

Example Requests

Read Couple Relationship Change History How to get the change history for the relationship.