Calling Insightly API v3.1 From the Right Pod, Under the Daily Cap
The key from User Settings is right, and every call still fails, because the request went to the wrong host. Insightly runs each account on a pod, and the pod is part of the base URL. Once that's sorted, the next thing to plan around is the daily request cap your plan sets for the whole account.
Base URL: https://api.{pod}.insightly.com/v3.1/, where the pod looks like na1. Your exact API URL sits right under your API key.
Auth: HTTP Basic with the API key Base64-encoded as the username and the password left blank. Every call runs with that user's permissions.
Docs: the interactive reference at api.insightly.com/v3.1/Help, with every endpoint and its parameters.
Limits: no more than 10 requests a second, plus a daily cap per account that depends on your plan. Over either, you get a 429.
Which Insightly API version reaches which records
A day of Insightly API calls, counted against the cap
The v3.1 reference has no webhook subscription endpoint. Check whether your plan's workflow automation offers a webhook action; without one, code learns about changes by asking, with a search on updated_after_utc, and every one of those asks comes out of the daily cap.
| Daily cap on the Plus plan | 40,000 |
|---|---|
| Change checks on 4 record types every 5 minutes (4 × 288) | −1,152 |
| Extra pages when a check finds more than one page of changes | −300 |
| Nightly full pass over 20,000 contacts (500 per page) | −40 |
| Updates written back to Insightly (one record per call) | −1,500 |
| Left for every other script and integration | 37,008 |
The cap is per account, not per integration, so everything that calls the API draws from the same pool. On Free, with 1,000 calls a day, the change checks alone would use it up. Professional allows 60,000 and Enterprise 100,000.
What Insightly code can do that AppConnect recipes don't
The API reads and writes the same records the app shows: leads, contacts, organizations and opportunities on the sales side, plus the projects module, tasks, events, and any custom objects your account has built. Custom fields are addressed by their field name, which the CustomFields endpoint lists, so business-specific data travels as easily as the standard fields.
There's no general bulk endpoint. Tags, dates and email domains can be updated in bulk, and everything else is a record per call, which is why the write line in the ledger above is the one to watch. AppConnect recipes and Insightly's Zapier app run separately from your code, and for which pairings they already cover, see Insightly integrations.
n-frames builds the jobs that need code: project and opportunity custom fields carried into accounting or ops tools as they change, change polling sized to your plan's cap, and one-off moves in or out of Insightly that keep custom objects intact.
Insightly API questions from the keyboard
Where do I find Insightly's API documentation?
At api.insightly.com/v3.1/Help, Insightly's interactive v3.1 reference. Your API key and the pod-specific API URL are both in User Settings, in the API section.
Do I need Insightly's AppConnect to use the API?
No. AppConnect is Insightly's separate recipe builder, priced by the tasks it runs. The API works without it, using only an API key, and code you write never touches AppConnect's task count.
Does Insightly's API support custom fields and custom objects?
Yes, on current versions. Use v3.1: version 2.3 and below have no Custom Objects endpoints, and 2.2 and below don't support every custom field type. Look up field names through the CustomFields endpoint before you write to them.
Is API access included on every Insightly plan?
Yes. Insightly says users on all plans can use the API. What changes by plan is the daily cap per account: 1,000 calls on Free, 20,000 on Legacy, 40,000 on Plus, 60,000 on Professional and 100,000 on Enterprise.
Can the Insightly API tell my code when a record changes?
The v3.1 reference doesn't list a webhook subscription endpoint, so code asks instead: a Search call with updated_after_utc returns records changed since the time you pass. For a push, check whether your plan's workflow automation offers a webhook action. AppConnect recipes and Insightly's Zapier app also start on record changes, and polling stays the fallback either way.
Who writes Insightly API integrations for small teams?
n-frames does, for companies that run sales and projects in Insightly and need its records, custom fields included, to reach accounting, operations or reporting without anyone exporting a spreadsheet.