> ## Documentation Index > Fetch the complete documentation index at: https://docs.moonup.gg/llms.txt > Use this file to discover all available pages before exploring further. # Edit an offer > Every field is optional and means "leave this alone" when absent. Sending `images` or `tags` replaces the whole list rather than adding to it. Changing `delivery_type` replaces the offer's unit pool. ## OpenAPI ````yaml /openapi.yaml patch /v1/offers/{id} openapi: 3.1.0 info: title: MoonUP Seller API version: 1.0.0 summary: List and manage your offers from your own tools. description: | Everything a seller's bot needs to keep a catalogue of listings up to date: read what a category expects, create a listing, restock it, pause it, archive it. This is the public surface. The cabinet's own screens — payouts, disputes, account settings — are not part of it and an API key does not reach them. ## Authentication Create a key in the cabinet under **Seller → API keys**. It is shown once. Send it on every request: ``` Authorization: Bearer moonup_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ``` There is nothing to exchange it for — no short-lived token sits in between. HTTPS only. Keep the key in an environment variable or your CI's secret store, never in a repository. A key may be pinned to a list of addresses when you create it (up to 16 addresses or subnets). An empty list means any address. ## Creating a listing Categories do not ask for the same things. An accounts listing needs a picture and a price; a currency listing needs a product and a stock; a gift-card listing may only be delivered instantly, with an activation code. Rather than describing that in prose that would go stale, every category answers for itself: GET /v1/offers/games/{game}/categories/{category_slug}/schema `attributes[]` is the category's own field list, and `requirements` is what the body of `POST /v1/offers` must carry for it. Both come from the code that validates the create call, so what you are told is what you are held to. A full pass looks like this: 1. `GET /v1/offers/games` — pick a game, keep its `slug`. 2. `GET /v1/offers/games/{game}/categories` — pick a category. 3. `GET /v1/offers/games/{game}/categories/{category_slug}/schema` — read `requirements` and `attributes`. 4. `POST /v1/offers/images/upload-url`, then PUT the bytes to the URL it returns. Repeat per picture, collect the public URLs. 5. `POST /v1/offers` — the listing is created as a `draft`. 6. `POST /v1/offers/{id}/submit` — it goes to moderation, then active. ## Rate limits | | Budget | |---|---| | Reads | 500 requests per minute | | Writes | 250 requests per minute | | Writes to one offer | 5 per minute and 10 per hour | Going over answers `429`. It is temporary: wait and retry, the key stays valid. Up to 5 keys per account — create the second one ahead of time so you can rotate without downtime. ## Errors Every failure answers with the same body, a stable snake_case code: ```json { "error": "seller_instructions_required" } ``` Branch on `error`, not on the message — there is no message. servers: - url: https://api.moonup.gg description: Production security: - api_key: [] tags: - name: Catalog description: | What can be listed, and what each category asks for. Public: these read without a key, so you can explore before you have one. - name: Offers description: Your own listings — create, edit, restock, pause, archive. paths: /v1/offers/{id}: patch: tags: - Offers summary: Edit an offer description: | Every field is optional and means "leave this alone" when absent. Sending `images` or `tags` replaces the whole list rather than adding to it. Changing `delivery_type` replaces the offer's unit pool. parameters: - $ref: '#/components/parameters/OfferID' requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/UpdateOffer' examples: reprice: summary: Drop the price and pause nothing else value: price: 3990 responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/Offer' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '409': $ref: '#/components/responses/Conflict' '429': $ref: '#/components/responses/RateLimited' components: parameters: OfferID: name: id in: path required: true schema: type: string format: uuid schemas: UpdateOffer: type: object description: | Every field optional; absent means "leave unchanged". `images` and `tags` replace the whole list when present. properties: title: type: string minLength: 8 maxLength: 128 description: type: string maxLength: 4096 price: type: integer format: int64 currency: type: string attributes: type: object additionalProperties: true images: type: array items: type: string format: uri tags: type: array items: type: string delivery_type: type: string enum: - instant - manual description: Changing this replaces the offer's unit pool. units: type: array items: type: object description: The stock a switch to instant starts with. manual_delivery_value: type: integer manual_delivery_unit: type: string enum: - minutes - hours - days manual_delivery_instructions: type: string maxLength: 2048 seller_instructions: type: string maxLength: 2048 delivery_method: type: string price_per_unit: type: integer format: int64 stock_quantity: type: integer format: int64 min_order_quantity: type: integer format: int64 Offer: type: object description: Your own listing, as the write calls answer with it. properties: id: type: string format: uuid seller_id: type: string format: uuid title: type: string description: type: string price: type: integer format: int64 currency: type: string attributes: type: object additionalProperties: true images: type: array items: type: string format: uri tags: type: array items: type: string delivery_type: type: string enum: - instant - manual manual_delivery_value: type: - integer - 'null' manual_delivery_unit: type: - string - 'null' manual_delivery_instructions: type: - string - 'null' status: type: string enum: - draft - pending_moderation - active - paused - reserved - sold - rejected - removed - archived created_at: type: - string - 'null' format: date-time updated_at: type: - string - 'null' format: date-time published_at: type: - string - 'null' format: date-time rejection_reason_code: type: - string - 'null' description: Why moderation refused it, when it did. rejection_note: type: - string - 'null' seller_instructions: type: string delivery_method: type: - string - 'null' price_per_unit: type: - integer - 'null' format: int64 stock_quantity: type: - integer - 'null' format: int64 min_order_quantity: type: - integer - 'null' format: int64 product_id: type: - string - 'null' format: uuid Error: type: object description: The one failure shape this API answers with. properties: error: type: string description: A stable snake_case code. Branch on this. examples: - seller_instructions_required required: - error responses: BadRequest: description: | The body or a parameter is wrong. `error` names which rule — e.g. `seller_instructions_required`, `bulk_fields_required`, `instant_requires_activation_code`, `title_too_short`, `invalid_attributes`, `invalid_image`. content: application/json: schema: $ref: '#/components/schemas/Error' examples: missing_field: value: error: seller_instructions_required Unauthorized: description: | The key is unknown, revoked, or the request came from an address outside the key's list. Which check failed is not disclosed. content: application/json: schema: $ref: '#/components/schemas/Error' examples: unauthorized: value: error: unauthorized Forbidden: description: | The key is valid but the account may not do this — it lacks the permission, or it is suspended (`account_suspended`). content: application/json: schema: $ref: '#/components/schemas/Error' NotFound: description: >- No such thing — or none you may know about, which answers the same on purpose. content: application/json: schema: $ref: '#/components/schemas/Error' examples: not_found: value: error: not_found Conflict: description: | The request was well formed, the offer is just not where it would have to be — `invalid_transition`, `offer_locked`, `sold_out`, `seller_on_vacation`. content: application/json: schema: $ref: '#/components/schemas/Error' RateLimited: description: One of the budgets is spent. Wait and retry; the key stays valid. content: application/json: schema: $ref: '#/components/schemas/Error' examples: rate_limited: value: error: rate_limited securitySchemes: api_key: type: http scheme: bearer description: Your API key, from the cabinet under **Seller → API keys**. ````