SuggestAPI Documentation
Contact us Open app
Reference

Service Limits

Understand the plan, storage, ingestion, and integration limits that can affect production use of SuggestAPI.

Copy page
Open in ChatGPT Open with page context Open in Claude Open with page context

SuggestAPI enforces a mix of fixed product constraints, plan-gated capabilities, and tenant-specific operational limits. This page brings those controls into one place so teams know what can block a rollout or write path in production.

Use this guide when you need to answer questions such as:

  • can this tenant create more indexes
  • how large can an import file be
  • what happens when a document cap is reached
  • which features require a paid plan

Limit types you should expect

Plan-gated limits

Some capabilities are enabled only on specific plans.

Current examples documented elsewhere in this docs set:

  • new index creation can be blocked by plan rules
  • integrations require a paid plan to list, create, or run
  • personalization behavior can depend on plan and schema settings

Storage limits

Storage-related limits control how much data can be written to an account or index.

Current documented constraints include:

  • account-level document limits
  • per-index document limits
  • file-size limits for upload-based ingestion

These limits may be plan-based, tenant-specific, or both.

Operational limits

Some limits exist to protect ingestion stability and job orchestration.

Current documented behavior includes:

  • ingestion waits for active jobs on the same index to finish before processing
  • large files can move through cloud-storage-backed ingestion paths
  • writes can be rejected when document limits are exceeded

Where limits show up

Limits are surfaced in a few different ways today:

  • endpoint-specific validation or rejected writes
  • plan-based access checks before an action runs
  • usage or billing surfaces in the app
  • support or account configuration for tenant-specific thresholds

If you are building automation around these rules, do not assume every limit is a universal constant. Some values are resolved per tenant.

Areas to validate before rollout

Index creation

Confirm the tenant can create and maintain the indexes required for the rollout. The current docs note that plan rules can block new index creation.

Related reference:

Bulk ingestion

Confirm the planned dataset fits both document-count constraints and upload-size constraints before running large imports.

Related reference:

Integrations and scheduled sync

If the rollout depends on integrations, verify the tenant has access to those flows before building around them. The current docs note that integrations require a paid plan.

Related reference:

What happens when you hit a limit

The exact response depends on the route, but the current docs already call out a few important cases:

  • document-cap enforcement can block writes with 409 responses
  • plan checks can block index creation or integration access
  • oversized uploads can fail when they exceed the configured limit

For ingestion-heavy workflows, treat limits as part of the control plane rather than as edge cases.

Before a production import, migration, or new tenant launch, verify:

  1. the tenant can create or maintain the required number of indexes
  2. the planned dataset fits account and per-index document limits
  3. the import file stays within the allowed upload size
  4. any required integrations are available on the tenant’s plan
  5. retry logic handles rejected writes and job serialization cleanly