Once you've established the employer, you are ready to register the employee (new hire) and employer administrators to the employer, which can happen at any time. As a reminder, employees must be configured before starting an I-9 for that employee.

Register Employee

To establish a new hire, register the employee by calling the /employers/{employerId}/employees POST endpoint. A successful request will return the employee's id that can then be used to generate the employee's access link to their I-9. Registering an employee can be completed in advance for an employee with a start date in the future, or it can be completed “just in time” right before the I-9 verification process begins.

When registering employees, you will also specify if an employee should not be eligible for Remote I-9 Section 2 verification within the employeeDocumentOptions object. (note: this is only applicable if you have Remote I-9 enabled by default).

Request

{
    "firstName": "Wendy",
    "lastName": "Kopp",
    "emailAddress": "[email protected]",
    "telephoneNumber": "202-789-4567",
    "address": {
        "zipCode": "85260-2662",
        "city": "Scottsdale",
        "streetAddress1": "14350 N 87th St",
        "streetAddress2": "Ste 250",
        "state": "AZ"
    },
    "socialSecurityNumber": "456-01-2785",
    "dateOfBirth": "1975-01-01",
    "employment": {
        "hireDate": "2025-05-18",
        "startDate": "2025-06-01",
        "status": "active",
        "employeeDocumentOptions": {
            "i9RemoteCounterSignAuthorized": true,
            "i9RemoteReverificationAuthorized": true
        }
    }
}

Request Elements

Below is the data necessary to register your employee within Symmetry.

Employment Object

The employment object contains key employment details for the employee, including important dates, current employment status, and document authorization options specific to Form I-9 processing.

Response

The response contains the employee identifier (id), along with the data from the request.

Below is an example of a successful response.

{
  "employee": {
    "id": "019721ce-cfcb-7224-972c-1234567",
    "emailAddress": "[email protected]",
    "firstName": "Wendy",
    "lastName": "Kopp",
    "socialSecurityNumber": "456-01-2785",
    "telephoneNumber": "202-789-4567",
    "dateOfBirth": "1975-01-01",
    "address": {
      "streetAddress1": "14350 N 87th St",
      "streetAddress2": "Ste 250",
      "city": "Scottsdale",
      "state": "AZ",
      "zipCode": "85260-2662",
      "country": "US"
    },
    "employment": {
      "hireDate": "2025-05-18",
      "startDate": "2025-06-01",
      "employeeDocumentOptions": {
        "i9RemoteCounterSignAuthorized": true,
        "i9RemoteReverificationAuthorized": true
      },
      "status": "active",
      "statusChangedBy": "0",
      "statusChangedAt": "2025-05-30T15:28:11.073Z",
      "onBoardingStarted": false
    }
  }
}

Response Elements

A successful response returns the employee object.

Employee Object

Employment Object

Employee Document Options Object

Address Object

Register Administrator

This one-time step is required to set up the employer administrator (HR, Compliance, or other executive functions at the employer) within that company who will administer Forms I-9 and take action on any documentation verification or E-Verify cases. Companies may have more than one administrator and administrators can be created at any time.

To create a new administrator, call the /employers/{employerId}/admins POST endpoint with the administrator details.

A successful call will return the administrator's ID that will then be used to generate the administrator's access to employer embedded experience.

📘

Email Address Unique Across Employers

Administrator records are linked across employers by email address. If the same email address is registered as an administrator at more than one employer (including across staging and production), the administrator’s name and profile information is shared between those employers. Retrieving the admin from either employer returns the most recently saved name, and updating the admin’s name at one employer updates it everywhere that email is registered.

If you need administrators to appear with different names per employer (for example, to distinguish a staging admin from a production admin), use unique email addresses for each. Email aliases (such as [email protected] versus [email protected] are treated as distinct.

Request

{
  "emailAddress": "[email protected]",
  "firstName": "AdminFirst",
  "middleName": "AdminMiddle",  
  "lastName": "AdminLast"
}

Request Elements

Below is the data necessary to register your administrator within Symmetry.

Response

The response contains the admin object, which includes the administrator's unique identifier.

Below is an example of a successful response.

{
  "admin": {
    "id": "01973711-0f1a-7325-9499-1234567",
    "firstName": "AdminFirst",
    "middleName": "AdminMiddle",  
    "lastName": "AdminLast",
    "emailAddress": "[email protected]"
  }
}

Response Elements

The fields below are returned in the admin object.

Admin Object

There are times when you may need to promote an employee to an administrator. Read about how to do that here: Promote Employee to Administrator.