List Estimates

GET

Query

Arguments

number

Page number

array of number

List of estimate type IDs

array of number

List of location IDs

array of number

List of estimate IDs

array of string

List of estimate document numbers

array of number

List of estimate status IDs

array of number

List of Employee IDs

array of number

List of client IDs

array of string

List of client names

array of string

List of Client phone numbers

array of date

Filter by creation date. Accepts an array with one or two ISO 8601 date-time values. If one value is provided, it represents the start (left) boundary. If two values are provided, they define a date range (start and end). Examples: ["2025-05-01T00:00:00Z"] — filter from May 1, 2025 onward. ["2025-05-01T00:00:00Z", "2025-05-02T00:00:00Z"] — filter between May 1 and May 2, 2025.

array of date

Filter by modification date. Accepts an array with one or two ISO 8601 date-time values. If one value is provided, it represents the start (left) boundary. If two values are provided, they define a date range (start and end). Examples: ["2025-05-01T00:00:00Z"] — filter from May 1, 2025 onward. ["2025-05-01T00:00:00Z", "2025-05-02T00:00:00Z"] — filter between May 1 and May 2, 2025.

array of date

Filter by "Scheduled from" date and time. Accepts an array with one or two ISO 8601 date-time values. If one value is provided, it represents the start (left) boundary. If two values are provided, they define a date range (start and end). Examples: ["2025-05-01T00:00:00Z"] — filter from May 1, 2025 onward. ["2025-05-01T00:00:00Z", "2025-05-02T00:00:00Z"] — filter between May 1 and May 2, 2025.

array of date

Filter by Due date" date and time. Accepts an array with one or two ISO 8601 date-time values. If one value is provided, it represents the start (left) boundary. If two values are provided, they define a date range (start and end). Examples: ["2025-05-01T00:00:00Z"] — filter from May 1, 2025 onward. ["2025-05-01T00:00:00Z", "2025-05-02T00:00:00Z"] — filter between May 1 and May 2, 2025.

string

Defines the sorting order of returned results. Use a field name to sort ascending or prefix it with a minus sign (-) to sort descending.

Field selectionChoose which fields should be included in the response. Learn more

string

Comma-separated response fields to include.

curl --request GET \ --url "https://connect.mindcloud.co/v1/universal/rOApp/0.0.8/actions/list-estimates" \ --header "Authorization: Bearer $MINDCLOUD_API_TOKEN" \ --get \ --data-urlencode 'connectionId=$CONNECTION_ID'

{ "success": true, "data": [ { "ad_campaign_id": 1, "asset_id": 1, "assignee_id": 1, "branch_id": 1, "client_id": 1, "custom_fields": "string", "due_date": "2026-05-07T12:00:00.000Z", "engineer_notes": "string", "estimated_price": "string", "malfunction": "string", "manager_id": 1, "manager_notes": "string", "order_type_id": 1, "payer_id": 1, "resource_id": 1, "resume": "string", "scheduled_for": "2026-05-07T12:00:00.000Z", "scheduled_to": "2026-05-07T12:00:00.000Z", "urgent": true } ], "meta": {} }

Query

Every app you connect,one REST pattern