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
1to2,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 100MB - 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
- For API access without caching: Maximum concurrent connections per hostname: 200
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 100MB - 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].
Files
Kuroco Files
-
The maximum file size that can be uploaded to Kuroco Files is around 80MB.
If you want to upload files larger than 80MB, consider integrating with GCS or S3. -
Please check the file types that can be used in the file manager.
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.
URL/Domain
Domain
- Japanese domains are not recommended as they depend on browser behavior.
- OK:
https://example.com - Not recommended:
https://てすと.com
- OK:
ltd Folder Token
- The
t=...token attached to files in the ltd folder has a validity period of 15 minutes. - The validity period cannot be changed.
GCS/S3 File Expiration
-
URLs for files saved in GCS/S3 have an expiration period.
Pattern Expiration API cache period is 7 days or less API cache period + 30 seconds API cache period is more than 7 days 7 days No API cache 30 minutes or session time + 30 seconds (whichever is shorter) Public folder No expiration cautionIf you use these URLs for a long time with SSG, etc., they may expire.
Restrictions for Free Users
The following restrictions apply to free users (users who have not registered payment information).
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.
Information -> Limiting the Number of Emails Sent by Free Users
Batch Processing
- Limited to approximately 100 executions per hour.
Information -> Limiting Batch Processing and API Sending for Free Users
API Sending
- Limited to approximately 1,000 requests per hour.
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.