tray-marcas

Manage product brand records through Tray API endpoints with CRUD operations.

14|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/tray-tecnologia/tray-api-claude-plugin --skill tray-marcas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tray-marcas
Source: https://github.com/tray-tecnologia/tray-api-claude-plugin/tree/main/skills/marcas
Command: npx skills add https://github.com/tray-tecnologia/tray-api-claude-plugin --skill tray-marcas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes and simplifies management of product brands for Tray-based e-commerce stores by providing clear, actionable API usage (list, retrieve, create, update, delete) and guidance on payload structure, pagination and filters so developers avoid common integration errors.

Core Features & Use Cases

  • CRUD for Brands: Endpoints and payload format for creating, reading, updating and deleting brand records under the Brand wrapper.
  • Listing with Pagination & Filters: Support for limit, page, and filters such as id, name and slug to efficiently query brand lists.
  • Integration Best Practices: Guidance on duplicate checks, slug behavior, image URL requirements and safe deletion to prevent data integrity issues.
  • Use Case: Add or verify brands before creating products, batch-import brand catalogs, or update brand logos and descriptions programmatically.

Quick Start

Use the tray-marcas skill to create a new brand named Nike with image URL https://exemplo.com/logo-nike.png and description Marca esportiva internacional.

Frequently Asked Questions about tray-marcas

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage product brands via the Tray API for an ecommerce store?

To manage product brands via the Tray API, you perform CRUD operations using endpoints that accept payloads wrapped under a Brand object containing name, slug, description, and image fields. An access_token query parameter is required for authentication.

What's the best way to list and filter brands in Tray with pagination?

Listing brands in Tray uses pagination and filters by applying limit, page, and query parameters like id, name, and slug. This filters brand records efficiently and returns paginated results to handle large e-commerce catalogs without fetching all data at once.

How do I create a new brand in Tray using the API payload wrapper?

Creating a brand in Tray requires sending a POST request with the payload wrapped under a Brand object. You must include the name, slug, description, and image URL fields, and pass your access_token as a query parameter to authenticate the request.

Does the Tray API support duplicate brand checks and safe deletion?

The Tray API supports duplicate checks and safe deletion through integration best practices. You can verify existing brands using slug and name filters before creating new records, and safely delete brands by following guidelines to prevent data integrity issues across your e-commerce store.

Why does my Tray API brand request require an access_token?

Your Tray API brand request requires an access_token passed as a query parameter to authenticate and authorize CRUD operations on the e-commerce store's product brand records. This token validates your access before the API processes any listing, creation, update, or deletion actions.