Postman's Free plan includes 5 integrations and 10,000 Postman API calls per month. Those numbers grow with each plan tier - and for most teams, these limits (not the user count) are what trigger the upgrade.
Limits by plan
| Plan | Integrations | Monthly Postman API calls |
|---|---|---|
| Free | Up to 5 | 10,000 |
| Solo | Up to 10 | 100,000 |
| Team | Up to 50 | Higher |
| Enterprise | Up to 100 | Higher |
Source: postman.com/pricing, verified on August 6, 2026.
Why the integration limit fills up fast
Five integrations sounds like plenty. In practice, connect one CI tool, one bug tracker, one chat notification, and one monitoring service - and the quota is nearly gone.
The critical detail: integrations are counted per account, not per workspace. A team running multiple projects can exhaust the limit on a single one.
Who the API call limit actually affects
10,000 calls a month is more than enough for someone driving Postman by hand. The limit matters for teams that automate their collections.
If your CI pipeline runs a collection on every build, a team doing 20 builds a day produces 600 runs a month. Depending on how many calls each run makes, the 10,000 ceiling arrives sooner than expected.
The add-on costs that get missed
Postman's pricing page also lists items that sit outside the plan fee. Monitoring costs $20 per team per month for 50,000 requests. Flows credits run $1 per 1,000 credits. AI credit overage starts at $0.05 per credit.
These look like small numbers, but they stack on top of the plan fee as usage grows. Budgeting on the per-user price alone gives a misleading answer.
A setup without those limits
In Lodos, API Post/Get is one of 30 modules, included in every plan - the free Standard plan too. There's no separate quota on collection count, folder organization, or environment variables.
Let's be clear: Lodos API Post/Get has no monitoring, no mock servers, and no automated collection runs. For a team running collections in a CI pipeline, Postman is still the right tool, and we make no claim otherwise.
Where Lodos makes sense is teams for whom API testing is part of the job: when you find a broken endpoint, opening a task, asking the team, and noting it in a document all happen in the same workspace.
Related reading
Is Postman still free for teams? · How much do SSO and encryption cost in Postman?