How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

ECI Solutions Registrant API

The Registrant API from ECI Solutions — 3 operation(s) for registrant.

ECI Solutions Registrant API is one of 194 APIs that ECI Solutions publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Registrant. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, API documentation, a support channel, authentication docs, and a changelog.

This API exposes 5 operations across 3 paths, and defines 31 schemas. It is described by OpenAPI 3.2.0, at version 1.0.39.

Requests are made against a single base URL, https://api.lassocrm.com/v1.

5 operations 3 paths 31 schemas 3 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.39
Base URL
https://api-erp.integrations.ecimanufacturing.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

ECI Solutions Registrant API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (JwtAuthorizer).

Paths & Operations 5

Across 3 paths, the API surfaces 5 operations — 3 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Registrant 5
GET
/registrants
List of registrants for a project
get_registrants 6 params → 200400401403500
POST
/registrants
Create a registrant
post_registrants body → 202400401403500
GET
/registrants/search
Search registrants by name, email, phone, nickname, externalId, rating or…
get_registrants_search 12 params → 200400401403500
PUT
/registrants/{registrantId}
Put registrants by id
put_registrants_by_id 1 param body → 200400401403404500
GET
/registrants/{registrantId}
Extended data for a registrant
get_registrants_by_id 1 param → 200401403404500

Schemas 31

The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are RegistrantWrite (23 properties), RegistrantRead (22 properties), AppointmentRead (12 properties), RegistrantPersonalInfo (10 properties). Each schema is shown below with its type and property counts.

SourceType
object
If the source type doesn't exist, it will be created
1 property
Question
object
Questions in Lasso are sorted into folders. You can use path to specify which folder the question should be saved to. Specifying the questionId will override n…
5 properties
AppointmentLinks
object
3 properties
Answer
object
Represents an answer for a question for the registrant
2 properties
RegistrantNoteLinks
object
1 property
RegistrantRead
object
22 properties
HistoryWrite
object
7 properties
PhoneWrite
object
3 properties
Project
object
2 properties
RegistrantAccepted
object
3 properties
SecondarySourceType
object
If the secondary source type does not exist, it will be created
1 property
Creator
object
Determines the user that created this entity based on an ordered set of Heuristics: - if creator is null or empty, then default to user: Lasso Autobot - if use…
3 properties
RegistrantWrite
object
23 properties
AddressWrite
object
7 properties
PhoneRead
object
4 properties
FollowUpProcess
object
If followUpProcessId is provided, the system will attempt to lookup the process by id, and fail if not found. If followUpProcessId is not provided, but followU…
2 properties
EmailWrite
object
3 properties
RegistrantNoteWrite
object
Contains a free-form text field. Limitations: 4-byte UTF-8 characters are not supported and will be stripped during write. This means that some emoticons and f…
3 properties
AddressRead
object
8 properties
EmailRead
object
5 properties
SalesRepWrite
object
When inputting a salesRep, you can provide a userId and the system will try to look up the salesRep by the ID. If no userId is provided but a first and last na…
4 properties
HistoryRead
object
7 properties
AppointmentSmsReminderRecipient
object
2 properties
AppointmentRead
object
12 properties
RegistrantNoteRead
object
Contains a free-form text field
4 properties
StandardError
object
A standard error response format.
3 properties
Rating
object
If rating does not exist, it will be created
1 property
RegistrantLinks
object
2 properties
RegistrantRelationshipRead
object
Contains a registrant's relationships
6 properties
RegistrantPersonalInfo
object
10 properties 2 required
RegistrantCreateMessage
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

eci-solutions-registrant-api-openapi.yml Raw ↑

Other APIs ECI Solutions publishes across the network.

ECI Solutions Account API
ECI Solutions Account Vault API
ECI Solutions Activation Code API
ECI Solutions Addresses API
ECI Solutions Analytics API
ECI Solutions AP Checks API
ECI Solutions Application API
ECI Solutions AR Invoice Details API
ECI Solutions AR Invoices API
ECI Solutions Attendance Ticket Details API
ECI Solutions Attendance Tickets API
ECI Solutions Authentication API
Where this information came from

This is an independent, third-party profile of ECI Solutions Registrant API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.