Skip to main content

​
“No operation with id ’…’”

describe_api or invoke_api was called with an operationId that doesn’t exist. Operation ids are stable but not guessable from the resource name alone — call search_apis first rather than constructing one. For example, deleting a lead is lead_trash, not lead_delete.

​
search_apis didn’t return the operation I expected

Ranking is a weighted keyword match over each operation’s real documentation, not semantic search — it has no synonym matching or stemming beyond exact and prefix matches. The right operation reliably appears within the top few results, but isn’t always first.
  • Read the summaries of results 2–5 before concluding nothing fits.
  • Try naming the record type (lead, transaction, task, call, email) together with the action (list, get, create, update).
  • If you already know the exact operationId from an earlier search_apis call in the same session, you can call describe_api or invoke_api directly without searching again.

​
I’m not sure whether to use the v1 or v2 version of an operation

Several resources — tasks, calendar, communication, transactions — have both a /v1.0 and a /v2.0 operation for what looks like the same action. They aren’t interchangeable, and neither version is universally preferred:
  • v2 task and calendar operations unify tasks and appointments under one id namespace and support fields v1 doesn’t.
  • v1 remains the only version for some actions.
Read both candidates’ describe_api output rather than assuming the higher version number is always correct.

​
A field name isn’t in describe_api’s schema

If a field you expect isn’t in an operation’s static schema, it may be a team-defined custom field — these are configured per team and can’t appear in any static schema. Call list_custom_fields before assuming the field doesn’t exist or guessing an id for it.

​
invoke_api returned a 401 or 403

The credential is missing, invalid, expired, or the underlying application isn’t authorized for that operation:

​
invoke_api returned a 404 for a record I expect to exist

This is usually a real, correct answer rather than an auth problem — for example lead_get returns 404 when the leadId doesn’t exist for the authenticated caller’s team, which includes leads that exist but belong to a different account. Double-check the id and which credential you’re using.

​
The response was truncated

A very large response is cut and prefixed with a NOTE: ... line explaining what was trimmed and how to get the rest (for example, by narrowing the query or paging). Read that line — don’t treat a truncated list as the complete result.

​
Still stuck?

Check Error Codes for the full list of API error codes, or see the API Reference for the same operations documented as plain REST calls.