Properties
| Name | Type | Description |
|---|---|---|
| accountId | string | Leadboxer accountId. |
| type | string | Set visibility of the segment. Possible values: USER : the segment will be private to user. ACCOUNT : the segment will be shared across the users of the account. |
| textFilter | string | Text-based filter expression used to filter result fields.Format: field|operator|value. Multiple filters are comma-separated. |
| numberFilter | string | Numeric filter expression used to filter results based on numeric fields. Format: field|operator|value. Multiple filters are comma-separated. Supported numeric operators include greaterthan, lessthan, |
| timeFilter | string | Time-based filter expression used to filter results by time field. Format: field|operator|value. Allowed fields (same as `timeField` parameter): - eventEsTimestamp : Last Seen - first_session_unix_tim |
| fieldFilter | string | Field-based filter used to include leads based on field presence. Format: operator|field1;field2 Allowed operator: - hasanyvalue Allowed fields: - firstName - lastName - email Multiple fields can be p |
| exitLinkFilter | string | Exit link filter used to include or exclude leads based on exit link values. Format: field|operator|value Supported operators: - contains - is - isnot - doesnotcontain Multiple values can be provided |
| leadscoreFilter | integer | Filters leads based on given minimum leadscore. |
| displayFilter | string | Display filter used to control which types of leads are returned. Supported values: - company - person - unidentified Selecting 'unidentified' returns leads that could not be identified as a company o |
| fromFilter | string | Filters leads based on specified from user |
| owner | string | Filters leads based on specified owner |
| hidden | string | Filters leads based on presetInclusionList |
| search | string | Keyword search |
| emailView | string | Email view type. Possible values : NONE, LEAD, ACCOUNT |
| notificationType | string | Set notification frequency. Possible values: NONE : Do not send any notification. DAILY : Send notification daily. WEEKLY : Send notification weekly. |
| notificationMailIds | string | List of comma separated email addresses for notification |
| mailTemplate | string | Set headlines for the notification email |
| format | string | Format for the segment notification. Possible values : html, csv |
| dayOfWeek | integer | Day of week on which weekly notification will be sent. Possible values include numbers from 1 to 7 (where 1 refers to Monday) |
| additionalCsvFields | string | List of comma separated fields to be included in CSV |
| sortBy | string | Field to sort result. Possible values : _score : records will be sorted as per leadscore. lastEvent : records will be sorted as per activity time. Default : _score |
| sortOrder | string | Sort order. Possible values : asc, desc Default : desc |
| viewType | string | View type. Possible values : B2B, B2C Default : B2B |
| timeField | string | |
| list | string | |
| csvSetName | string |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/leadboxer-com/json-schema/leadboxer-com-update-segment-request-schema.json",
"title": "UpdateSegmentRequest",
"x-generated": "2026-10-30",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/leadboxer-com-api-openapi.yml#/components/schemas/UpdateSegmentRequest",
"required": [
"accountId",
"emailView",
"notificationType",
"type"
],
"type": "object",
"properties": {
"accountId": {
"type": "string",
"description": "Leadboxer accountId."
},
"type": {
"type": "string",
"description": "Set visibility of the segment.<br/><br/><b>Possible values:</b><br/><b>USER</b> : the segment will be private to user.<br/><b>ACCOUNT</b> : the segment will be shared across the users of the account.",
"enum": [
"USER",
"ACCOUNT"
]
},
"textFilter": {
"type": "string",
"description": "Text-based filter expression used to filter result fields.Format: field|operator|value. Multiple filters are comma-separated."
},
"numberFilter": {
"type": "string",
"description": "Numeric filter expression used to filter results based on numeric fields. Format: field|operator|value. Multiple filters are comma-separated. Supported numeric operators include greaterthan, lessthan, is, isnot, between, and notbetween. The between and notbetween operators use the format min-max."
},
"timeFilter": {
"type": "string",
"description": "Time-based filter expression used to filter results by time field. Format: field|operator|value.\n\nAllowed fields (same as `timeField` parameter):\n- eventEsTimestamp : Last Seen\n- first_session_unix_timestamp : First Seen\n\nSupported operators:\n- exactly → integer value (0 = Today, 1 = Yesterday)\n- lessthan → integer value (e.g. 6 = last 7 days)\n- between → date range in format dd/MM/yyyy-dd/MM/yyyy\n\nLocale settings are taken into account while interpreting dates and returning results."
},
"fieldFilter": {
"type": "string",
"description": "Field-based filter used to include leads based on field presence.\n\nFormat:\noperator|field1;field2\n\nAllowed operator:\n- hasanyvalue\n\nAllowed fields:\n- firstName\n- lastName\n- email\n\nMultiple fields can be provided using semicolons."
},
"exitLinkFilter": {
"type": "string",
"description": "Exit link filter used to include or exclude leads based on exit link values.\n\nFormat:\nfield|operator|value\n\nSupported operators:\n- contains\n- is\n- isnot\n- doesnotcontain\n\nMultiple values can be provided using semicolons."
},
"leadscoreFilter": {
"maximum": 100,
"minimum": 0,
"type": "integer",
"description": "Filters leads based on given minimum leadscore.",
"format": "int32"
},
"displayFilter": {
"type": "string",
"description": "Display filter used to control which types of leads are returned.\n\nSupported values:\n- company\n- person\n- unidentified\n\nSelecting 'unidentified' returns leads that could not be identified as a company or a person.\n\nMultiple values can be provided using semicolons."
},
"fromFilter": {
"type": "string",
"description": "Filters leads based on specified from user"
},
"owner": {
"type": "string",
"description": "Filters leads based on specified owner"
},
"hidden": {
"type": "string",
"description": "Filters leads based on presetInclusionList"
},
"search": {
"type": "string",
"description": "Keyword search"
},
"emailView": {
"type": "string",
"description": "Email view type.<br/>Possible values : NONE, LEAD, ACCOUNT<br/>",
"enum": [
"NONE",
"LEAD",
"ACCOUNT"
]
},
"notificationType": {
"type": "string",
"description": "Set notification frequency.<br/><br/><b>Possible values:</b><br/><b>NONE</b> : Do not send any notification.<br/><b>DAILY</b> : Send notification daily.<br/><b>WEEKLY</b> : Send notification weekly.",
"enum": [
"NONE",
"DAILY",
"WEEKLY"
]
},
"notificationMailIds": {
"type": "string",
"description": "List of comma separated email addresses for notification"
},
"mailTemplate": {
"type": "string",
"description": "Set headlines for the notification email"
},
"format": {
"type": "string",
"description": "Format for the segment notification.<br/>Possible values : html, csv"
},
"dayOfWeek": {
"type": "integer",
"description": "Day of week on which weekly notification will be sent. Possible values include numbers from 1 to 7 (where 1 refers to Monday)",
"format": "int32"
},
"additionalCsvFields": {
"type": "string",
"description": "List of comma separated fields to be included in CSV"
},
"sortBy": {
"type": "string",
"description": "Field to sort result.<br/>Possible values :<br/><b>_score</b> : records will be sorted as per leadscore.<br/><b>lastEvent</b> : records will be sorted as per activity time.<br/>Default : _score"
},
"sortOrder": {
"type": "string",
"description": "Sort order.<br/>Possible values : asc, desc<br/>Default : desc"
},
"viewType": {
"type": "string",
"description": "View type.<br/>Possible values : B2B, B2C<br/>Default : B2B"
},
"timeField": {
"type": "string"
},
"list": {
"type": "string"
},
"csvSetName": {
"type": "string"
}
}
}
Work with this as data
Every JSON Schema 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 schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.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.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/leadboxer-com-update-segment-request"
All schemas
curl "https://apis.io/api/v1/json-schemas?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.
A second provider on the same verified email joins the account you already have.