I’d like to request an escalation for portal 146624382 (free plan, EU1).
My meeting scheduler page fails for every new visitor. The booking API (POST /meetings-public/v1/book) returns a 402:
"Portal 146624382 has exceeded its OBJECT_CREATION CONTACT limit of 1000 (LimitExceededException)
Latest correlationId: 01a0e7d9-adb3-77c4-bef5-077ad9e1e418
Context: a lemlist integration pushed me over the 1,000-contact limit of the free plan.
I have since:
disconnected the integratio
deleted all contacts: Data Model > Limits now shows 0 contact records
permanently deleted some records from the recycle bin (982 remaining there)
The block has not been lifted. HubSpot support chat confirmed this looks like an entitlement/usage-sync issue and advised me to post here.
Could someone from the HubSpot team trigger a backend recalculation or removal of the OBJECT_CREATION CONTACT block on this portal?
Sorry to hear you’re running into that issue. I’ve reached out to our internal team to investigate your portal and confirm the behavior we’re seeing there. I’ll reach back out once I have any updates for you!
You are almost certainly on a stale entitlement / usage counter, not on a live “you still have 1000 contacts” count. Meeting public book creates a contact (or tries to), so it hard-fails on OBJECT_CREATION CONTACT even when the UI list looks empty.
While Sam’s internal check runs, this is the recovery order that usually clears it:
Empty the recycle bin completely. Soft-deleted contacts still count against creation entitlement on many portals. Data Model showing 0 active contacts is not enough if ~982 remain in the bin. Purge the bin to 0, wait a few minutes, retry one test book with a brand-new email.
Confirm nothing is still writing contacts. Lemlist disconnected is good. Also check other forms, ads, native syncs, and private apps with crm.objects.contacts.write. One leftover writer will re-trip the free-plan cap as soon as the counter moves.
Re-check Limits after purge. Settings → Data Management → Data Model → Limits (contacts). If active is 0 and bin is 0 but book still returns the same 402 + correlationId, that is the entitlement-sync bug Support described. Keep the latest correlationId for the ticket.
Escalation packet for HubSpot staff (you already posted the portal id). Include: portal 146624382, EU1, free plan, exact 402 body, latest correlationId, “active contacts 0 / recycle bin 0 after purge”, and that Meetings POST /meetings-public/v1/book is the failing surface. Ask explicitly for an OBJECT_CREATION CONTACT entitlement recalculation (usage counter reset), not another UI delete.
Stabilize ownership after unblock. On free tier, keep a hard cap alarm (contacts approaching 900) and keep high-volume enrichment tools off the portal. Otherwise the same 402 returns the next time an integration backfills.
So: purge recycle bin to zero first, retest book, then push Support/Community staff for entitlement recalc with the correlationId if it still 402s. There is no public portal toggle that clears this counter yourself.
If you can update whether the recycle bin is fully empty after purge (and whether a fresh book still 402s), the next step is obvious for Sam’s internal thread.
My meeting scheduler now accepts bookings from new contacts again. For anyone hitting the same 402 “OBJECT_CREATION CONTACT limit” error on a free portal: even with 0 active contacts, the ~980 soft-deleted contacts in the recycle bin were still blocking contact creation. The UI only lets you permanently delete them one by one, so I purged them in bulk with a private app (crm.objects.contacts.read/write scopes): list them with GET /crm/v3/objects/contacts?archived=true, then call POST /crm/v3/objects/contacts/gdpr-delete for each ID. Once the bin was empty, bookings worked right away.
