​

Assign Template Resources

POST /api/v1/content/projects/:projectId/template-assignments/:pageId

​

Path parameters

​

Request body

​

Behavior

• The target page’s type is derived from its existing assignments and must be resource-backed.
• A resource whose handle already points at this page is an idempotent no-op (returned under existing).
• All-or-nothing. Every requested handle is checked first. If any handle already belongs to a different live page, the whole request is rejected with 409 CONFLICT (the clashing handles in details.conflicts) and nothing is written — a mixed batch never leaves partial assignments. A resource is never repointed away from another page.
• New resources are created as assignment rows pointing at pageId, in a single transaction.
• All lookups and writes are scoped strictly to projectId; the endpoint never touches another project’s pages.

​

Example

curl -X POST \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  "https://studio.weaverse.io/api/v1/content/projects/clx1abc23def456ghij/template-assignments/clz5wxy12abc345gift" \
  -d '{
    "assignments": [
      { "handle": "summer-sale", "shopifyResourceId": "gid://shopify/Collection/123" },
      { "handle": "winter-drop",  "shopifyResourceId": "gid://shopify/Collection/456" }
    ]
  }'

​

Response

{
  "object": "template_assignments",
  "pageId": "clz5wxy12abc345gift",
  "type": "COLLECTION",
  "requested": 2,
  "created": [
    { "handle": "summer-sale", "locale": "", "assignmentId": "asg_1" }
  ],
  "existing": [
    { "handle": "winter-drop", "locale": "", "assignmentId": "asg_0" }
  ]
}

​

Errors