ECI Solutions

ECI Solutions Employee API

The Employee API from ECI Solutions — 2 operation(s) for employee.

GitHub OpenAPI

Operations 2

GET /api/v2.1/employees Get a list of Employees from the ERP system that match the given filters #
GET /api/v2.1/employees/{id} Get an Employee from the ERP system that matches the given unique ID #

Documentation

📖
APIReference
https://integrations.ecimanufacturing.com/api.html?family=erp
📖
Documentation
https://integrations.ecimanufacturing.com/
📖
APIReference
https://integrations.ecimanufacturing.com/api.html?family=jb2
📖
APIReference
https://integrations.ecimanufacturing.com/api.html?family=m1
📖
APIReference
https://integrations.ecimanufacturing.com/api.html?id=management-v1
📖
APIReference
https://integrations.ecimanufacturing.com/authenticate.html
📖
Authentication
https://raw.githubusercontent.com/api-evangelist/eci-solutions/refs/heads/main/authentication/eci-solutions-authentication.yml
📖
APIReference
https://platform.lassocrm.com/api/

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/eci-solutions/refs/heads/main/openapi/eci-solutions-employee-api-openapi.yml

Other Resources

🔗
Support
https://www.ecisolutions.com/support/
🔗
OAuthScopes
https://raw.githubusercontent.com/api-evangelist/eci-solutions/refs/heads/main/scopes/eci-solutions-scopes.yml
🔗
OpenIDConnect
https://cognito-idp.us-east-1.amazonaws.com/us-east-1_9IYBf4TpD/.well-known/openid-configuration
🔗
ChangeLog
https://raw.githubusercontent.com/api-evangelist/eci-solutions/refs/heads/main/changelog/eci-solutions-changelog.yml
🔗
Webhooks
https://raw.githubusercontent.com/api-evangelist/eci-solutions/refs/heads/main/asyncapi/eci-solutions-lasso-registrant-webhooks.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/eci-solutions-employee-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

eci-solutions-employee-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: ERP API v2.1 Employee API
  description: Provides a common API surface for accessing ECI ERP products.
  contact:
    name: ECI Manufacturing Division Integration Team
    url: https://www.ecisolutions.com/support/
  version: 3.5.585+b1e45fd230
servers:
- url: https://api-erp.integrations.ecimanufacturing.com:443
  description: Production
security:
- Bearer: []
tags:
- name: Employee
paths:
  /api/v2.1/employees:
    get:
      tags:
      - Employee
      summary: Get a list of Employees from the ERP system that match the given filters
      description: 'Gets a list of Employee.


        ## Supported ERPs

        - M1

        - JobBOSS²

        - Macola

        - Deacom

        ## Resource Features

        Feature |Supported |Notes

        ------------|------------|------------

        Filter Expressions|**Yes**|

        Sort Expressions|**Yes**

        Field Selection|**Yes**

        Pagination|**Yes**

        UniqueID|uniqueID|

        ## Features by Field

        Field |Filterable |Sortable |Supported ERPs

        ------------|------------|------------|------------

        employeeID|Yes|Yes|M1, JobBOSS², Macola, Deacom

        firstName|Yes|Yes|M1, JobBOSS², Macola, Deacom

        lastName|Yes|Yes|M1, JobBOSS², Macola, Deacom

        title|Yes|Yes|M1, JobBOSS², Macola, Deacom

        supervisorEmployeeID|Yes|Yes|M1, JobBOSS², Macola, Deacom

        payRate|Yes|Yes|M1, JobBOSS², Macola, Deacom

        deptID|Yes|Yes|M1, JobBOSS², Macola, Deacom

        shiftID|Yes|Yes|M1, JobBOSS², Macola, Deacom

        isActive|Yes|Yes|JobBOSS², Deacom

        uniqueID|Yes|Yes|M1, JobBOSS², Macola, Deacom

        rowVersion|Yes|Yes|M1, JobBOSS², Macola, Deacom'
      parameters:
      - name: fields
        in: query
        description: A comma-separated list of fields to include in the result.
        schema:
          type: string
      - name: sort
        in: query
        description: A comma-separated list of <a href='#sortexpr'>sort expressions</a>.
        schema:
          type: string
      - name: take
        in: query
        description: Limit the number of results being returned
        schema:
          minimum: 0
          type: integer
      - name: skip
        in: query
        description: The number of results to skip. Combine with 'take' to fetch records in pages
        schema:
          minimum: 0
          type: integer
      - name: count
        in: query
        description: '<a href=''#countparam''>Data and count</a> response behavior '
        schema:
          maximum: 2
          minimum: 0
          type: integer
      - name: filters
        in: query
        description: See <a href='#filterexpr'>Filter Expressions</a> for query string syntax. The Test UI and any generated code tool may expose filter parameters as a dictionary of name/value pairs, but if creating a raw HTTP request, they must be provided on the querystring as defined in the Filter Expression section.
        style: form
        schema:
          type: object
          additionalProperties:
            type: string
        examples:
          Empty:
            description: No filters applied
          'Example #1':
            description: A dictionary of name/value pairs that will be serialized as querystring parameters in the format ```name[operator]=value```
            value:
              employeeID[eq]: abc123
              firstName[eq]: abc123
              lastName[eq]: abc123
              title[eq]: abc123
              supervisorEmployeeID[eq]: abc123
              payRate[gte]: 123
              deptID[eq]: abc123
              shiftID[eq]: abc123
              isActive[eq]: true
              uniqueID[eq]: cc90686b-399e-4094-b431-fa462f84b0a8
              rowVersion[gte]: 123
      responses:
        '200':
          description: Success
          content:
            text/plain:
              schema:
                $ref: '#/components/schemas/EmployeeListResponse'
            application/json:
              schema:
                $ref: '#/components/schemas/EmployeeListResponse'
            text/json:
              schema:
                $ref: '#/components/schemas/EmployeeListResponse'
      operationId: getApiV21Employees
      x-operation-id-source: derived
  /api/v2.1/employees/{id}:
    get:
      tags:
      - Employee
      summary: Get an Employee from the ERP system that matches the given unique ID
      description: 'Gets a Employee by unique ID.


        ## Supported ERPs

        - M1

        - JobBOSS²

        - Macola

        - Deacom

        ## Features by Field

        Field |Supported ERPs

        ------------|------------

        employeeID||M1, JobBOSS², Macola, Deacom

        firstName||M1, JobBOSS², Macola, Deacom

        lastName||M1, JobBOSS², Macola, Deacom

        title||M1, JobBOSS², Macola, Deacom

        supervisorEmployeeID||M1, JobBOSS², Macola, Deacom

        payRate||M1, JobBOSS², Macola, Deacom

        deptID||M1, JobBOSS², Macola, Deacom

        shiftID||M1, JobBOSS², Macola, Deacom

        isActive||JobBOSS², Deacom

        uniqueID||M1, JobBOSS², Macola, Deacom

        rowVersion||M1, JobBOSS², Macola, Deacom'
      parameters:
      - name: id
        in: path
        description: The ID of the Employee
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Success
          content:
            text/plain:
              schema:
                $ref: '#/components/schemas/Employee'
            application/json:
              schema:
                $ref: '#/components/schemas/Employee'
            text/json:
              schema:
                $ref: '#/components/schemas/Employee'
      operationId: getApiV21EmployeesById
      x-operation-id-source: derived
components:
  schemas:
    EmployeeListResponse:
      type: object
      properties:
        data:
          type:
          - array
          - 'null'
          items:
            $ref: '#/components/schemas/Employee'
          readOnly: true
        resultCount:
          type: integer
          format: int32
      additionalProperties: false
    Employee:
      title: Employee
      type: object
      properties:
        employeeID:
          type: string
        firstName:
          type: string
        lastName:
          type: string
        title:
          type: string
        supervisorEmployeeID:
          type: string
        payRate:
          type: number
          format: double
        deptID:
          type: string
        shiftID:
          type: string
        isActive:
          type: boolean
        uniqueID:
          type: string
        rowVersion:
          type: integer
          format: int64
  securitySchemes:
    Bearer:
      type: oauth2
      description: OAuth 2.0 Client Credentials Flow with API Users issued from Integration Engine Management Console
      flows:
        clientCredentials:
          tokenUrl: https://api-user.integrations.ecimanufacturing.com/oauth2/api-user/token
          scopes:
            openid: openid