Integration fields limits

Developing with Prismic
1

Hi gang,

We’ve started exploring Integration fields, specifically through the “Push data to Prismic” method.

So far it seems like it would work really well for what we need, but there’s some information I could not find online.

  1. What is the limit for the Integrations API and what counts as a hit? (as seen in the Billings section: “Integration fields: The number of requests made through integration fields.”)
  2. What counts as a hit? Only when we update/create/delete content, or every time the Integration field is used?
  3. How many items can it contain? We’re looking at needed 500,000+ and would need to adjust should the limit be lower. I found this post that referenced 100,000, but it’s now 5 years old. Could I please get confirmation?
  4. What others costs should we be considering, if any?

Thanks very much!

3

Hey @r.cantin,

Thanks for reaching out!

  1. What is the limit for the Integrations API and what counts as a hit? (as seen in the Billings section: “Integration fields: The number of requests made through integration fields.”)

These are the limits, they are also on our Pricing page:

  • Free / Small / Starter: limit = 100 SKU (by default)
  • Medium: limit = 500 SKU (100SKU by default - paid overage up to 500)
  • Platinum (Monthly): limit = 500 SKU (100SKU by default - paid overage up to 500)
  • Platinum (Yearly): limit = 10,000 SKU (100SKU by default - paid overage up to 10,000)
  • Enterprise: Custom (100SKU by default - paid overage)
  1. What counts as a hit? Only when we update/create/delete content, or every time the Integration field is used?

The number of SKUs exposed to Prismic through Integration Fields is what is counted. From the Pricing page says:

A SKU (“Stock Keeping Unit”) is any unique item you connect to Prismic via an integration, for example, a product from Shopify. One SKU can appear in multiple integration fields but is only counted once toward your limit.

  1. How many items can it contain? We’re looking at needed 500,000+ and would need to adjust should the limit be lower. I found this post that referenced 100,000, but it’s now 5 years old. Could I please get confirmation?

Gathering information on that and I'll get back to you to confirm!

  1. What others costs should we be considering, if any?

Nothing else on IF on Prismic's side :slight_smile:

4

Thank you for all this! I’ll wait for your confirmation on #3 which is the last snag, but so far it seems to cover our needs very well.

I assume the SKUs are counted when the API is queried within Prismic by our Editors and not when viewed on the FE/that data is fetched for rendering, so if we need approx 300 items, and those rarely change, we should be covered.

1 Like
5

Got the information, the limit of 100,000 stands :slight_smile: It can be upped on custom Enterprise plans if that's something that would make sense for your project. Thanks for asking those questions, we need to document this better!

Just to clarify, the number of SKUs are counted from what Prismic queries from your catalog. If you use 300, then you should make sure Prismic can only read 300. If you feed Prismic a catalog of 50,000 for example, we will count 50,000 (not just the 300 of those that are used within a page).

1 Like
6

Oh… so it’s directly linked to the number of items in the catalogue then? Is there a way to only offer a sub-selection?

7

You'd have to make a selection on your end, you can choose what gets linked to Prismic by making your own catalogs: Integration — Prismic Docs. Maybe that'll help!

8

Thanks for confirming all the above so promptly, Ezekiel, much appreciated!

1 Like
9

Happy to help! Don't hesitate to reach out if you have anymore questions :slight_smile:

1 Like