> ## Documentation Index > Fetch the complete documentation index at: https://dev.puppetvendors.com/llms.txt > Use this file to discover all available pages before exploring further. # Approve products > Approve up to 100 pending products in one call, as draft or active. Each product gets its own result, and the push to Shopify is queued, so read the product afterwards to see its final status. To find products waiting for review, call `GET /products?status=pending`. Requires the `admin:products:write` permission. ## OpenAPI ````yaml openapi-merchant.json POST /products/approve openapi: 3.0.0 info: title: PuppetVendors Merchant API V2 version: 2.0.0 description: >- The endpoints reachable with a merchant API key (`mk_live_…`), minted from Settings → API Access in the PuppetVendors admin. A merchant key administers users and vendors, and renews its own token. Everything else in the V2 API, including orders, products, payouts, fulfillments and documents, stays on the v1 API token and is refused here with a 403. Keys are revealed once at creation; rotating one leaves the previous key working for a 24 hour grace window. contact: name: PuppetVendors Support url: https://puppetvendors.com license: name: Proprietary servers: - url: https://production-api.puppetvendors.com description: Production - url: http://localhost:8082 description: Local development security: - bearerAuth: [] tags: - name: Auth description: Authentication endpoints for obtaining and refreshing API tokens - name: Portal - Auth description: Vendor portal authentication endpoints (vendor user login, token refresh) - name: Products description: Product management and synchronization - name: Merchant Products description: >- Every vendor's products in your store, read and edited with a merchant API key, plus bulk approval and rejection of pending products. A missing product returns 404 `PRODUCT_NOT_FOUND`. - name: Orders description: Order retrieval and management - name: Payouts description: Vendor payout information - name: Fulfillments description: Order fulfillment operations - name: Reports description: Vendor sales reports and analytics - name: Vendors description: Vendor management operations - name: Settings description: Settings endpoints for vendor configuration and management - name: Users description: User account management - name: Shop description: Shop configuration and settings - name: Commissions description: Commission rate management - name: Integrations description: Vendor integration configuration endpoints - name: Line Items description: Order line item operations paths: /products/approve: post: tags: - Merchant Products summary: Approve products description: >- Approve up to 100 pending products in one call, as draft or active. Each product gets its own result, and the push to Shopify is queued, so read the product afterwards to see its final status. To find products waiting for review, call `GET /products?status=pending`. Requires the `admin:products:write` permission. operationId: merchantApproveProducts requestBody: required: true content: application/json: schema: type: object required: - productIds - publishAs properties: productIds: type: array minItems: 1 maxItems: 100 items: type: string description: >- 1 to 100 product ids (ObjectId, Shopify GID or numeric id); duplicates are removed publishAs: type: string enum: - draft - active description: >- Matched in any case (ACTIVE and DRAFT, as PATCH /{productId}/status takes them, are accepted) and normalized to lowercase responses: '202': description: One result per product id content: application/json: schema: type: object properties: success: type: boolean enum: - true data: type: object properties: results: type: array items: type: object required: - productId - outcome properties: productId: type: string outcome: type: string enum: - queued - refused request: type: string enum: - productCreate - productUpdate code: type: string message: type: string '400': description: Invalid body (more than 100 ids, malformed id, unknown publishAs) content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Missing, invalid or revoked token content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '403': description: Not a merchant API key, or the key lacks admin:products:write content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '503': description: >- APPROVAL_PUBLISH_FAILED, the queue is unreachable and nothing was approved (see Retry-After). Only when at least one id could be approved; a call whose every id is refused answers 202 with the refusals. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - bearerAuth: [] components: schemas: ErrorResponse: type: object required: - success - error properties: success: type: boolean enum: - false description: Indicates the request failed error: type: object required: - message properties: message: type: string description: Human-readable error message example: Resource not found code: type: string description: >- Stable machine-readable error code. The frontend uses this as its localisation key (e.g. errors.api.). Server errors always report INTERNAL_SERVER_ERROR. example: NOT_FOUND errorId: type: string description: >- Correlation id for support/log lookup. Present on opaque 5xx responses so a user can quote a reference for the underlying (server-side logged) error. example: err_1783365360839_j281w7b details: type: object description: >- Additional client-error context (e.g. field-level validation errors). Never populated for server errors. securitySchemes: bearerAuth: type: apiKey in: header name: x-access-token description: >- JWT minted from a merchant API key (`mk_live_…`) by POST /authenticate. Send the token value directly, with no "Bearer" prefix. Tokens last 14 days and can be renewed at POST /refresh-token; revoking the key refuses the next request made with any token minted from it. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.