Errors & limits

​

Error format

{
  "jsonrpc": "2.0",
  "id": 1,
  "error": { "code": -32000, "message": "Short description of the error." }
}

​

Limits

• Upstream timeout: each upstream call is bounded at 15-20 seconds depending on the connector. GSC, Uniconta, e-conomic, Dinero, Meta Ads, LinkedIn Ads and Billy use 15 s; Shopify, HubSpot CMS, HubSpot Email and CVR use 20 s. A slow provider surfaces as an error rather than hanging.
• Reconnect on revoke: a revoked or invalid upstream credential surfaces as a “reconnect required” error; reconnect the connector in the portal.

• Rows per request: up to 25,000 (limit / rowLimit).
• Pagination: use startRow in search_analytics_query to fetch further.
• Dates: always YYYY-MM-DD.
• Properties: you can only reach properties your authorized Google account already has access to. Use list_sites to see them.

• Page size: list tools take pagesize (default 20, max 1000) and skippages; not every list tool accepts filter/sort. See the e-conomic reference.

• Rate limit: Dinero allows about 100 requests per minute per organisation. A 429 is retried once, then surfaces as DineroRateLimitError.
• Dinero Pro required: the public API only works for organisations on Dinero Pro. A non-Pro organisation returns 403 on every call except list_organizations and validate_connection (both only enumerate organisations, so they work without Pro); the connector surfaces the 403 as DineroProRequiredError.
• Deprecated endpoint: an HTTP 480 from Dinero signals a deprecated endpoint about to be removed and surfaces as DineroApiError. 4xx responses are never retried. See the Dinero reference.

​

Data freshness (Google Search Console)

• Expect a delay of a couple of days on the newest numbers.
• In search_analytics_query you can control this with dataState:
  • final: only fully collected data.
  • all: includes preliminary (fresh but unstable) data.