Get a relationship
Retrieve one relationship through either of its two people.
This endpoint also answers QUERY, with the same parameters sent in the request body. How QUERY works.
Path parameters
Sent as JSON. Anything not listed here is ignored.
The vault both people live in, named either by the readable name it reports as slug or by its id.
One of the two people, named either by their slug or by their id. A contact addressed through the wrong vault answers 404.
The id of the relationship. It is reached through either of its two people, and through anybody else answers 404.
Returns
A relationship object.
The relationship.
Always relationship. It names the kind of record, so a caller holding several kinds can tell them apart without looking at where they came from.
The id of this record, as a string even when it reads as a number. It is what every endpoint naming this record takes.
Everything the record holds.
What the link is.
The id of the relationship type.
The name of the relationship type.
True when both people hold the same role, as partners do.
The person holding role_a.
The id of the contact.
The readable name of the contact, which addresses it as well as its id.
The name of the contact, as it is shown.
True for somebody who exists only through a relationship and has no record of their own.
The role this person holds, which is the type's role_a.
The person holding role_b.
The id of the contact.
The readable name of the contact, which addresses it as well as its id.
The name of the contact, as it is shown.
True for somebody who exists only through a relationship and has no record of their own.
The role this person holds, which is the type's role_b.
current or ended.
When it started, written as a year, a month and a day, or null.
When it ended, or null. Always null while the relationship is current.
When the relationship was recorded, as a count of seconds since 1970.
When it last changed, as a count of seconds. Equal to created_at until it first changes.
Where to find this record.
The absolute address this record is read from.
Rate limit
Sixty requests per minute, per user, shared by every key and device. Every answer carries the budget left in X-RateLimit-Remaining.
Keys act as you, with exactly the access you have. Make one per integration so you can revoke it alone.