
Cloudinary notification verification uses the entire notification body together with its timestamp. If middleware parses JSON and your handler later reconstructs a different string, that string may no longer match what was signed. Preserve the original body for verification, using the documented SDK helper and the correct server-side key context before trusting the event.
Key Takeaways
- Equivalent JSON values do not establish an identical signed string.
- Notification signatures and upload-response signatures use different payload contracts.
- A valid signature does not by itself identify the correct creative task or approve its result.
Inspect the body before middleware rewrites it
The notification-signature guide identifies the X-Cld-Signature and X-Cld-Timestamp headers and the entire-body verification input. Trace the request through your framework and identify where the original body becomes available and where JSON parsing occurs.
Keep that original input available to the verification step according to the framework's supported raw-body mechanism. Changing whitespace or reconstructing property order can change a string even when the parsed values look equivalent. This is a diagnostic possibility, not proof that every failed signature comes from parsing.
Do not expose raw client notifications, secrets or signed addresses in a public support thread. A private note can identify the framework version, handler stage and verification outcome without publishing the request's contents.
Use the notification contract and the configured verification key
Prefer the current SDK's verify_notification_signature procedure and its supported validity setting. Supply the actual original body, signature and timestamp in the form required by that installed SDK. Keep the secret on the server.
The signature quick reference distinguishes notification verification from checking the signature in an API's JSON response. The latter's public-ID/version payload is not interchangeable with the notification body. Selecting the wrong helper or reconstructing an upload-signature parameter list is therefore a separate issue to investigate.
Also confirm the applicable verification key. Cloudinary documents a dedicated notification key when configured, otherwise the oldest active key in the product environment. Check the existing configuration through the authorized administrator; changing the selected key is a separate operation, not an automatic debugging step.
Keep freshness and task identity in the decision
Verify timestamp freshness within the chosen supported validity window as well as the signature. Investigate clock or processing delays when appropriate rather than disabling validation to make a request appear successful.
After verification, associate the event with the expected asset, environment and pending application task. A genuinely signed event for another upload still does not complete the task currently visible in a customer's editor.
Use the approval-record distinction after processing: authenticated completion and human acceptance describe different states. If a later retrieved file contains the wrong response bytes, diagnose that download separately.
Exercise explicit handler outcomes on a test endpoint
Proposed cases are an authorized original notification, an altered body, an unacceptable timestamp and a valid event associated with another test task. Record verification and task-transition outcomes separately. This article has not sent any of those requests or verified a deployed handler.
Accept the integration only when validation uses the original documented inputs, failed checks do not mark work complete, and a verified event is matched to its intended task. Keep creative approval and any later publication as separate decisions.
Related tasks
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
- Why Does My Downloaded Image Open as a Web Page?
Sources and scope
- Cloudinary: Verifying notification signatures: Notifications include X-Cld-Signature and X-Cld-Timestamp. Verification uses the entire body and timestamp with the applicable server-side secret, or the SDK verification helper; timestamp freshness also matters.
- Cloudinary: Signatures quick reference: The notification signing payload is the full response body plus its timestamp, unlike the public_id/version payload used for verifying a JSON API response signature.
Documentation-based handler-design guidance. No notification endpoint was changed, no request was replayed, and no application authentication was tested. The cases are proposed checks for an authorized test environment.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.