List projects with the Everhour API

Lists the projects the user has access to, with the client id, billing type, rates and budget with its usage. Ids carry the integration prefix, such as as:1234567890 for Asana or ev:1234567890 for projects created in Everhour. Pages start at 1, and a page shorter than limit is the last one.

Identifier
everhour_list_projects

The request

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

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

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
querystringNoText matched against project names.
limitintegerNoProjects per page.
pageintegerNoPage number, starting at 1.

Supported connections

Your customer connects their Everhour 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/everhour_list_projects. It becomes your agent's tool definition with no conversion.

Other Everhour tools

See all 15 tools

Toolkits in the same category

See all 100 toolkits

See Connect applied to your product.

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