Organization and group IDs are also listed under My Account > Developer > Organization & Group IDs.
| Method | URI |
|---|---|
| GET | /v4/organizations |
| GET | /v3/organizations (deprecated) |
Returns the organizations the member belongs to, with the groups in each organization. No parameters are required.
| Method | URI |
|---|---|
| GET | /v4/organizations/{id} |
| GET | /v3/organizations/{id} (deprecated) |
Returns an organization's details, including its groups. The member must belong to the organization.
{
"id": 6,
"name": "ChamberForge",
"created_at": "2018-02-09 17:37:26",
"updated_at": "2022-01-22 17:35:13",
"groups": [
{
"id": 33,
"name": "Northern Virginia Referral Group",
"created_at": "2021-11-10 10:05:38",
"updated_at": "2022-02-10 21:14:31"
}
]
}
In v4 the same organization is returned inside the data field of the response envelope.
The endpoints above act as a member. An organization can also connect a system of its own, such as a CRM, with an organization API token. The token belongs to the organization, not to a person.
Organization Administrators and Staff create and revoke tokens under the organization's Settings > API. See API Tokens. Send the token like any other token:
Authorization: Bearer {organization_token}
Accept: application/json
An organization token only works on the /v4/organization/... endpoints below, and a member's token does not work on them. A request without a valid organization token returns 401 with the code UNAUTHORIZED.
| Method | URI | Description |
|---|---|---|
| GET | /v4/organization | The organization the token belongs to |
| GET | /v4/organization/members | The members referrals can be sent in the name of |
| GET | /v4/organization/referrals | Referrals the organization sent or received |
| GET | /v4/organization/referrals/{id} | One of those referrals |
| POST | /v4/organization/referrals | Send a referral |
GET /v4/organization/members returns the organization's Employees, Staff and Administrators with their id, name, email and role. Only these members can be named as the sender of a referral.
GET /v4/organization/referrals returns referrals sent by the members above and referrals reported to the organization, most recently updated first.
| Parameter | Description |
|---|---|
| type | sent or received. Leave it out for both. |
| status | One or more status numbers separated by commas: 1 Created, 2 Work in Progress, 3 Recalled, 4 Lost, 5 Won. |
| updated_since | Only referrals updated on or after this date and time. |
| offset | Number of referrals to skip. Default 0. |
| limit | Number of referrals to return. Default 50, maximum 200. |
The response's meta field holds offset, limit and total.
Each referral includes id, referral_date, status, status_name, sent_by_organization, received_by_organization, from and to (each with type, id and name), is_private, description, the lead fields, total_amount, created_at and updated_at.
description and the lead fields) are returned as null.GET /v4/organization/referrals/{id} returns a single referral in the same shape, or 404 if the referral is not one of the organization's.
POST /v4/organization/referrals sends a referral in the name of one of the organization's Employees, Staff or Administrators.
| Parameter | Description |
|---|---|
| referral_date | Required. Not later than tomorrow. |
| from_id or from_email | Required. The sender, who must be an Employee, Staff or Administrator of the organization. |
| to_id or to_email | Required. The recipient. With to_email, a person without an account is invited by e-mail. |
| description | Optional, up to 5,000 characters. |
| lead_name, lead_email, lead_phone, lead_company | Optional lead details. |
| do_not_notify_user | Optional. Send true to skip the notification to the recipient. |
The sender and the recipient cannot be the same person. The referral is created with the status Created, and the response returns it with the status code 201. Validation errors return 422 with error.fields.