About this block

Rate Limits Table publishes the part of the API contract vendors usually hide in docs nobody links. A four row table maps resources to limits per plan, and a side panel lists the three response headers that expose limit state, with the burst policy spelled out in the lede. The closing line, support raises limits for migration weekends without a sales call, converts an operational page into a sales argument.

Two small arrays drive the whole block, limits and headers.

When to use

Reach for this block deep on developer pages, after the webhook reference, where serious integrators are sizing production load. It belongs on the same page as plan pricing so the per plan columns map to something purchasable.

A natural flow around it on a Marketing Pro page:

Before

• Webhook events and the rest of the integration surface

After

• Pricing where the plan columns resolve to prices
• Status proving the platform holds under the limits it sells

What you can display

One strong use is your production rate limits with the real header names. Other contracts:

• Storage quotas. Rows per plan across objects, files, seats.
• Concurrency limits. Parallel jobs, builds, or exports.
• Fair use policy. The numbers behind the word unlimited.

Tip: the burst policy is the difference between a limit that reads as generous and one that reads as a trap, publish it.