Upload and manage codes with the API

Overview

Codes are the stock inside a database: the keys, licenses, vouchers, or files Keysender delivers when an order is paid. The Code endpoints let your software top up a database in bulk, check what is available or already used, flag a code to go out first, and remove a code that should never be sent.

Before you start

Make sure you have:

• A bearer token from POST /login and the base URL https://panel.keysender.com/api/v1.0.
• The id of the database you are filling (see Manage inventory databases with the API).

A code has these fields: id, type (1 text, 2 file), value, status (0 available, 1 used), keyusage, sendfirst (1 to deliver before other codes), filename, and the optional unit_cost, currency, purchase_date, and expiration_date.

Steps

Upload text codes

1. Send POST /code?database_id=123 with a JSON array of objects, one per code:

curl -X POST "https://panel.keysender.com/api/v1.0/code?database_id=123" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '[{"value": "AAAA-BBBB-CCCC"}, {"value": "DDDD-EEEE-FFFF", "unit_cost": 4.2, "currency": "EUR"}]'

2. Send at most 1,000 codes per request. Codes beyond the first 1,000 in one request are not stored, and the response does not warn you, so batch larger uploads.
3. The response is the array of stored codes with their new ids.

Upload a file as a code

1. Send POST /code?database_id=123&name=manual.pdf with the raw file as the body and its real content type (for example Content-Type: application/pdf). Allowed types: PDF, JPG, PNG, GIF, TXT, CSV, TSV, XLS, MP3, EPUB. Maximum 80 MB.
2. The response is an array with one code of type: 2 and filename set.

List codes

1. Send GET /codes?database_id=123. Add page and pagesize (maximum 1000), and filter with filter=[{"status":0}] for available codes, [{"status":1}] for used ones, or [{"value":"AAAA"}] to find one.

Mark a code used, or send it first

1. Send PUT /code with all three fields: {"id": 456, "status": 1, "sendfirst": 0}. Both status and sendfirst must be present even when only one changes.

Delete a code

1. Send DELETE /code with {"id": 456}. Only an available code (status: 0) can be deleted; a used code stays for the order history.

Confirm it works

After an upload, GET /codes?database_id=123&filter=[{"status":0}] includes the new values, and the database's available count under Inventory in the panel has grown by the same number.

If it still is not working

• Fewer codes stored than sent: the request exceeded 1,000 codes. Send the remainder in a new request.
• 422 on the file upload: the content type is not in the allowed list, or the file exceeds 80 MB.
• A delete is refused: the code is already used.
• Still stuck? Submit a ticket with the database id, the count you sent, and the response.