GET
/
api
/
hris
/
v1
/
benefits
/
{id}
curl --request GET \
  --url https://api.bindbee.dev/api/hris/v1/benefits/{id} \
  --header 'Authorization: Bearer <token>' \
  --header 'x-connector-token: <x-connector-token>'
{
  "id": "018b18ef-c487-703c-afd9-0ca478ccd9d6",
  "remote_id": "123321",
  "modified_at": "2021-10-16T00:00:00Z",
  "raw_data": {
    "key_1": "Platform dependent data 1",
    "key_2": "Platform dependent data 2"
  },
  "custom_fields": {
    "category_group": "REG",
    "disability_type": "ASBERG",
    "hire_date": "1991-03-16T00:00:00",
    "hire_source": "REFER",
    "nationality": "USA",
    "original_hire_date": "1991-03-16T00:00:00"
  },
  "employee": "<any>",
  "plan_name": "401(k) Plan",
  "provider_name": "Metlife",
  "benefit_plan_type": "MED",
  "frequency": "SEMIMONTHLY",
  "employee_contribution": 22.27,
  "company_contribution": 77.22,
  "start_date": "2023-10-18T00:00:00Z",
  "effective_date": "2023-10-18T00:00:00Z",
  "end_date": "2024-10-16T00:00:00Z",
  "employer_benefit": "<any>"
}

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

​
x-connector-token
string
required

Path Parameters

​
id
string
required

Query Parameters

​
include_raw_data
boolean
default:false

Whether to include the original data Bindbee fetched from the third-party to produce these models.

​
include_custom_fields
boolean
default:false

Whether to include custom fields in the response.

​
expand
string

Which relations should be returned in expanded form. Multiple relation names should be comma separated without spaces. You can also specify required fields in [] for each relation name.

Response

200
application/json

Successful Response

The Benefit object is used to represent a benefit that an employee has enrolled in.