Skip to main content

Restrictions in Kuroco

Restrictions in Kuroco​

Explaining the restrictions in using Kuroco.

Contents​

ID​

  • IDs such as topics_id are automatically assigned and may not start from 1 due to the specification of inheriting data from the account creation source.

Number of Contents​

  • topics_id takes values from 1 to 2,147,483,647. In theory, it is possible to register up to 21 billion contents, but we have not verified the operation with that many contents. Depending on the data items, performance is expected to be within 1 million records. Please consult with us if you plan to use more than that.

Order​

  • Values that can be entered for ordering are up to 9 digits.

Slug​

  • Slugs can only be registered up to 2048 characters.
  • Only alphanumeric characters and hyphens (-) can be used. Japanese characters are not supported.

Text Character Limit​

  • Unlimited - however, within 200,000 characters per field is recommended

Indexing​

  • Content fields with "indexing enabled" can only be registered up to 2048 characters.

CSV Import​

  • CSV files within 80MB - however, within 30,000 items is recommended (expansion planned)

Content Definition Count​

  • Unlimited - however, within 1,000 is recommended

Content Category Count​

  • Unlimited - however, within 1,000 per content definition is recommended

API​

Concurrent Connections​

  • There is a limit on the maximum number of concurrent connections to the API, and exceeding the limit will result in a 429 error.
    • For API access without caching: Maximum concurrent connections per hostname: 200
      Assuming an endpoint that takes 300ms to respond, receiving more than 200 requests within 0.3 seconds, most customers will not reach the limit.
    • For cached API access: No limit on concurrent connections

Write Requests to the Admin API / Admin MCP​

  • Write requests to the Admin API (/direct/rcms_api/admin_api/) and Admin MCP (/direct/rcms_api/admin_mcp/) are limited to 8 requests per 2 seconds per site. Exceeding the limit returns a 429 error (the Retry-After header states how many seconds until a retry is admitted).
    • Read requests are not covered by this limit (the concurrent connection limit above still applies).
    • An MCP client may expand a single instruction into several tool calls and send them in parallel, so issue writes one at a time or use a bulk operation that handles several records in a single call.
  • A single call can process up to 200 records, or up to 100,000 records per job when queued with async=true.
    info

Endpoint Count​

  • Unlimited - however, within 1,000 is recommended

API Key Count​

  • Unlimited - however, within 1,000 is recommended

Query String​

  • The maximum length of the Query String is around 8000 characters.

Members​

Member Count​

  • Track record of 10 million members - however, prior consultation is recommended for 300,000 or more members

CSV Import​

  • CSV files within 80MB - however, within 30,000 items is recommended (expansion planned)

Password​

  • Allowed characters: Alphanumeric characters (case-sensitive) and some symbols (-, _, &)
  • Full-width characters cannot be used.
  • Minimum and maximum character limits can be changed in [Preferences] -> [Site Management].
    info

Files​

Kuroco Files​

Kuroco Front​

  • The maximum file size that can be uploaded to Kuroco Front is 30MB.
  • Server-side programs (PHP, CGI, Perl, Ruby, etc.) do not work.
  • SSI (Server Side Include) and .htaccess cannot be used.
    info

URL/Domain​

Domain​

  • Japanese domains are not recommended as they depend on browser behavior.
    • OK: https://example.com
    • Not recommended: https://てすと.com

ltd Folder Token​

GCS/S3 File Expiration​

  • URLs for files saved in GCS/S3 have an expiration period.

    PatternExpiration
    API cache period is 7 days or lessAPI cache period + 30 seconds
    API cache period is more than 7 days7 days
    No API cache30 minutes or session time + 30 seconds (whichever is shorter)
    Public folderNo expiration
    caution

    If you use these URLs for a long time with SSG, etc., they may expire.

    info

Restrictions for Free Users​

The following restrictions apply to free users (users who have not registered payment information).

info

The following users are exempt from these restrictions:

  • Customers who have registered a credit card under "Billing Information"
  • Customers whose payment method is set to "Invoice issued by Diverta"

Email Sending​

  • Limited to approximately 100 emails per hour.
  • Users who are using their own SendGrid API key with a custom domain email address are exempt from this restriction.
info

Information -> Limiting the Number of Emails Sent by Free Users

Batch Processing​

  • Limited to approximately 100 executions per hour. The count is the number of batch runs started (registered), not the requests issued inside a batch.
  • A single batch run times out after 4 hours by default (6 hours for batches that run a Smarty template). Split large workloads with paging so that each run stays short.
info

Information -> Limiting Batch Processing and API Sending for Free Users

API Sending​

  • Limited to approximately 1,000 requests per hour.
info

Information -> Limiting Batch Processing and API Sending for Free Users

Support

If you have any other questions, please contact us or check out Our Slack Community.

Contact form
Join Kuroco Slack community