List deals with the Agendor API

Lists and searches the deals of the account, 10 per page by default, in data, with meta.totalCount and the next page in links.next. Each deal brings its status, stage, funnel, owner and the organization or person it belongs to.

Identifier
agendor_list_deals

The request

POST https://connect.reportei.com/api/tools/agendor_list_deals/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "title": "<title>"
  }
}

Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.

Parameters

ParameterTypeRequiredDescription
titlestringNoBeginning of the title.
dealStatusintegerNoStatus of the deals: 1 ongoing, 2 won, 3 lost.Values: 1, 2, 3
dealStageintegerNoId of a stage, from the dealStages of List funnels.
organizationintegerNoId of an organization, from List organizations.
personintegerNoId of a person, from List people.
userOwnerintegerNoId of the user who owns the deals, from List users.
createdAtGtstringNoReturns deals created after this date and time, in ISO 8601.
updatedAtGtstringNoReturns deals updated after this date and time, in ISO 8601.
endAtGtstringNoReturns deals finished after this date and time, in ISO 8601.
withCustomFieldsbooleanNotrue includes the custom fields of each deal.
pageintegerNoPage number, starting at 1.
per_pageintegerNoDeals per page, up to 100. The default is 10.

Supported connections

Your customer connects their Agendor account once, with one of the modes below. The same connection serves every tool of the toolkit.

API key

Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.

The response

On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.

Ready for AI agents

This tool's input is a JSON Schema, available at GET /api/tools/agendor_list_deals. It becomes your agent's tool definition with no conversion.

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.