# Add a Census Members and their dependents can be added to a group through the Create Members endpoint ([API docs](https://docs.ideonapi.com/#group-member-management-group-member-management-put)). When quoting, include all eligible employees in the census. Eligibility rules typically rely on this assumption. Ideon's group quoting API does not include any fields to designate employees as waiving coverage. Ideon's API is versioned by endpoint. The Create Members endpoint is not versioned alongside the group quoting workflow — v6 is the latest available version of this endpoint and should be used for v9 group quoting. This page refers to the v6 schema for the Create Members endpoint. ## Configuring Requests When quoting a group, premiums are determined by member data — including dependents, location, age, and tobacco status. Notes on important fields are included below. * **Member Location** `zip_code` and `fips_code` - the home location of the member. This is not used for quoting in most scenarios, but is evaluated for certain eligibility rules based on the member's home or work location. * **Date of Birth** `date_of_birth` and `dependents[].date_of_birth` - premiums and eligibility are determined using the age of a member and their dependents at the effective date of coverage. * **Last Used Tobacco** `last_used_tobacco` and `dependents[].last_used_tobacco` - tobacco status is dependent on state and carrier, both in terms of the cutoff date to consider an individual a user as well as the potential impact on premiums. If an individual has never used tobacco, or the last use date is unknown, *null* can be passed. * **Cobra and Retiree** `cobra` and `retiree` - if unknown, *false* can be passed. * **Location ID** `location_id` - the internal identifier for the location the member works at, as returned in the "Create a Group" endpoint. * **Dependents** * **Relationship** `dependents[].relationship` **-** valid dependent relationships are enumerated in the [API docs](https://docs.ideonapi.com/#header-add-the-census). Certain plans and carriers allow different dependent types; ineligible dependents for a given plan will result in eligibility flags. The dependent relationship *other* can be used as a fall-back to bypass all eligibility rules. * **Same Household** `dependents[].same_household` - dependent relationships can be valid or invalid based on whether or not the dependent lives in the same household as the member. A sample request with fields required for small group medical quoting, for reference: {% code title="PUT /groups/\/members" %} ```json { "members": [ { "zip_code": "10010", "fips_code": "36061", "date_of_birth": "1970-01-01", "gender": "F", "cobra": false, "last_used_tobacco": null, "retiree": false, "external_id": "003", "location_id": "", "dependents": [ { "date_of_birth": "1970-01-01", "gender": "M", "last_used_tobacco": null, "relationship": "spouse", "same_household": true } ] } ] } ``` {% endcode %} ## Additional Information ### Adding or Replacing Members The census endpoint supports both POST and PUT methods. For small group quoting applications, we typically recommend using PUT to fully replace census members. This helps maintain accurate syncing of censuses and limits overall API request volume. ### Member and Dependent Identifiers Separate `id`s are returned for all members and their dependents. These identifiers are surfaced in subsequent endpoints to refer to specific members or their dependents. Notably, member and dependent `id` values are referenced in the `member_exceptions` array returned in the quote results and documented in the [Retrieve Premium and Eligibility Results section](/quote-and-select/quote-groups/small-group-medical/retrieve-premium-and-eligibility-results.md), identifying which specific members or dependents triggered a given member-level eligibility exception for a plan. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://ideonapi.gitbook.io/quote-and-select/quote-groups/small-group-medical/add-a-census.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.