Documentation Index
Fetch the complete documentation index at: https://docs.hellocobi.com/llms.txt
Use this file to discover all available pages before exploring further.
Important: The shop category model has dependencies on both the shop and
category models. The
shop_id field must reference an existing shop and the
category_id field must reference an existing category. It’s recommended to
upload shop and category data before uploading shop category mappings.Schema
Field Descriptions
Required Fields
| Field | Type | Format | Description |
|---|---|---|---|
shop_category_id | string | UUID | Unique identifier for the shop category mapping |
shop_id | string | UUID | ID of the shop (must reference an existing shop) |
category_id | string | UUID | ID of the category (must reference an existing category) |
region | string | - | Geographic region (2-letter country code, e.g., “CA” for Canada) |
Optional Fields
| Field | Type | Format | Description |
|---|---|---|---|
created | string | date-time | Timestamp when the record was created |
updated | string | date-time | Timestamp when the record was last updated |
is_deleted | boolean | - | Flag indicating if the record is marked as deleted |
Example
Best Practices
- UUID Format: Use valid UUID v4 format for all ID fields
- Data Dependencies: Ensure shop_id references an existing shop and category_id references an existing category
- Region Codes: Use ISO 3166-1 alpha-2 country codes (e.g., “CA” for Canada, “US” for United States)
- Data Consistency: Ensure consistent data across all shop category mapping records