Upload multiple items

Use the Rewind Toy Exchange ChatGPT connection or an API integration to list a collection. Each item becomes its own listing. The connection submits items one at a time; there is currently no CSV or spreadsheet upload button on the website.

Option 1: Upload a batch with ChatGPT

Open ChatGPT with the Rewind Toy Exchange — Collector Marketplace connection enabled and sign in when prompted.
Attach your item photos. Label each group clearly, such as Item 1, Item 2 and Item 3, so photos stay with the correct toy.
For each item, provide its title, category, condition, price in USD, description, city/state, and shipping cost or local pickup. Include missing pieces, damage and whether packaging is sealed. Supply 1–10 photos per item.
Ask ChatGPT to prepare the listings and show you a summary before publishing. Review the details and approve the specific batch.
After approval, ChatGPT can create each listing in sequence and report which succeeded. If a result is uncertain, check your listings before retrying.

Copy this request into ChatGPT

Help me list these items on Rewind Toy Exchange using the connected marketplace tools. Keep each item and its photos separate. Ask me for missing details, then show me all titles, descriptions, prices, conditions and shipping costs for approval before publishing. After I approve, publish each listing and tell me which succeeded. Check my listings before retrying any uncertain result.

Choose the account method before starting: ChatGPT-created listings belong to the connected ChatGPT identity. They are separate from listings created with your Google/email website account. Use the same method to manage listings later. Choose the API option below if the batch must belong to your existing website account.

Option 2: Upload a batch with an API integration

Prepare one listing record per item, including its own photos. A developer can convert a spreadsheet or inventory file into these records; the API does not accept a CSV file directly.
Authenticate with your website Firebase account using the instructions below.
Validate each record, then send a separate POST request to /api/listings for each approved item. Sending a JSON array in one request is not supported.
Save the returned listing ID for each successful item. Stop on errors, retain the failed records, and check existing listings before retrying an uncertain request.
Stay within 30 listing writes per hour per account, shared by create, edit and remove actions. Split larger collections across later batches.

Listings are published or queued according to marketplace availability. Use one clearly marked TEST item first if you are trying a new integration.

Required policy acceptance

Before creating or updating a listing, read the marketplace terms and privacy notice and expressly accept them. Your API integration must send policyVersion: "2026-11-03" with each create or update request. When using ChatGPT, ask it to show the policies and obtain your agreement before submitting the batch. A missing or outdated version is rejected; do not add acceptance without the seller’s authorization.

Technical setup and reference

Create and manage your own listings through the API or MCP. All existing seller permissions, validation and listing limits apply.

Test with the API

Sign in to the website using Google or a verified email account.
Your integration must sign in with the same Firebase project using the Firebase Authentication SDK and obtain an ID token with await user.getIdToken(). Refresh tokens through the SDK; ID tokens expire after about one hour. Keep credentials and tokens private.
Send Authorization: Bearer YOUR_FIREBASE_ID_TOKEN and Content-Type: application/json to the endpoints below. A ChatGPT account is not required for this API method.

GET /api/listings?mine=1 — your listings
POST /api/listings — create and publish
PATCH /api/listings — edit your listing; include its id, status (active or paused), and all required listing fields
DELETE /api/listings — remove your listing using {"id":"LISTING_UUID"}
GET /api/automation — tool schemas and allowed values

Firebase client configuration

This public configuration identifies the website’s authentication project. It is not an admin credential.

{
  "apiKey": "AIzaSyAJdy5GbOzNjefZfOOarAV08B7Qc6FcxLc",
  "authDomain": "rewind-toy-exchange.firebaseapp.com",
  "projectId": "rewind-toy-exchange",
  "appId": "1:584094776426:web:eb0586d09fb2cfa0751e13"
}

Example listing body

{
  "title": "TEST — Transformers figure",
  "category": "Transformers",
  "price": 25,
  "condition": "Used / Complete",
  "description": "Test listing. Replace this text with an accurate item description.",
  "location": "Feasterville Trevose, PA",
  "images": [
    "data:image/jpeg;base64,REPLACE_WITH_COMPRESSED_PHOTO"
  ],
  "shipping": 500,
  "delivery": "shipping"
}

Price is in dollars; shipping is in cents. Supply 1–10 actual JPEG, PNG or WebP photos as base64 data URLs, each at most 360,000 characters. The placeholder above must be replaced. Up to 30 listing writes per hour are permitted. After an uncertain create result, check your listings before retrying to avoid duplicates.

MCP

The MCP endpoint is https://toy-vault-exchange.diecast2.chatgpt.site/mcp. Use the Site’s generated plugin in ChatGPT where available. Tools: listing_options, my_listings, create_listing, update_listing and remove_listing. The connection requires authentication and access to the plugin; an endpoint URL alone does not grant access.

MCP uses the connected ChatGPT identity; the bearer-token API uses your website account. These are separate accounts. To manage the same listings as your Google/email website login, use the API method.

Friend’s test

First fetch your listings, then create one item clearly titled TEST with a real photo. Confirm it appears on the marketplace, edit or pause it, and remove it when finished. Creation publishes the listing immediately, subject to existing marketplace availability. Do not purchase the test item.