Idempotent calls
Overview
To ensure the reliability of API calls, some OpenAPIs support idempotency by passing a unique identifier in the X-Idempotent-Request-ID request header. This feature prevents duplicate requests caused by network failures or repeated submissions.
Usage
When you make an OpenAPI request, add the following field to the request header:
Field name:
X-Idempotent-Request-ID.Field value: A custom unique string. The recommended format is a standard 32-character UUID.
Usage notes
Length limit:
X-Idempotent-Request-IDmust not exceed 50 characters.The recommended format is a standard UUID, for example:
c0e77df6-2af3-4c60-8440-abf447845491.
Empty value handling:
The idempotency feature is disabled if the
X-Idempotent-Request-IDheader is omitted, or if its value isnull, an empty string (""), or consists only of whitespace characters (for example," ").
Validity period limit:
If you reuse the same ID within its validity period, the server returns the cached result from the original request. The response body is identical to the original, except for the
requestId.If you reuse an ID after its validity period expires, the server processes it as a new request and returns a new result.
Idempotent APIs
API name | API full path | Idempotency required | Validity period |
CreateTask | /rpa/openapi/raas/task/CreateTask | No | 180 seconds |