What the API access evidence can tell you.

Guide

Use this before you automate the work.

Step 1

Scope and selection

We selected 200 SaaS products used by small and growing businesses across CRM, marketing, forms, commerce, finance, HR, projects, collaboration, support, scheduling and field services. Enterprise editions are included where businesses may encounter them. This is an editorial sample, not every SMB vendor or a representative market survey.

• Reviewed on 2026-10-08 (UTC). Dates are source review dates, not vendor effective dates.
• Only official vendor pricing, developer documentation or vendor-owned help articles are cited.
• Each record includes a short verbatim quote and a link to its primary source.

Step 2

Plans and uncertainty

Documented plans are explicit availability statements in reviewed sources, not necessarily the lowest qualifying plan. Rate-limit tables may establish access for particular endpoints. We do not infer public API access from a third-party integration or assume that webhooks share API eligibility.

• Not documented as of 2026-10-08 in reviewed sources means those pages did not establish the plan. It does not mean the vendor has no API.
• Historical documentation, regional pricing, partner access and endpoint restrictions are noted beside the evidence.
• No vendor login, API credential, live endpoint test or sales confirmation was used. Private agreements, add-ons, fees and limits may differ.

Step 3

Vendor correction and disputes

The tracker links to a correction form that asks for the product, official source URL and proposed change. The existing TeamShift request intake retains the submission for review and requires phone contact consent. A submission does not automatically edit or publish a record.

• A reviewer checks the claimed tier against current primary documentation before changing the dataset.
• Accepted updates replace the source or scoped claim and record the new verification date in the same versioned dataset.
• If sources conflict or a plan cannot be verified, keep it unresolved and explain the scope instead of making a negative access claim.

Step 4

Reuse the evidence

The tracker offers CSV and JSON downloads generated from the same source used by the visible page. Cite the vendor source and verification date when using a record. Recheck the current plan before purchase or integration.

• No account signup is required to read or download the tracker.
• This snapshot does not measure vendor reliability, integration quality or an API surcharge.
• Sources and plan names can change; vendor corrections provide a review path, not a promise of continuous monitoring.

Questions

Before you hand this off