Ruwana Developer Documentation
Give every logical production request one stable idempotency key.
Ruwana production endpoints require an Idempotency-Key. Platform binds that key to the authenticated organization, endpoint and canonical request so network retries do not become accidental duplicate production.
Header contract
Idempotency-Key: order-1842-hero-imageAccepted format: 8–128 characters using letters, digits, period, underscore, colon or hyphen.
Create one key
Generate a stable key for the logical business operation, not for each HTTP attempt.
Retry the same request
If transport fails, send the same endpoint, inputs and key again.
Reuse the existing result/state
Successful requests return their existing result; running PRO, Video, Motion and Avatar requests return the same durable identity.
Never mutate under the same key
Changing canonical request content or endpoint under an existing key returns HTTP 409 idempotency_key_conflict.
Media expiry does not reset idempotency. Replaying a successful request does not regenerate production and does not extend the fixed media-retention deadline.