Receive a file at one chosen object path without giving the sender the service’s access keys. The recipient must use a tool that sends the file with HTTP PUT to the generated link.

Create the intended link

1. Open the storage service’s Share links section.
2. Select the intended Bucket.
3. Enter the exact File path within that bucket.
4. Select Upload (receive a file) under Link type.
5. Choose Expires after and generate the link.
6. Check the displayed expiry and verify the intended operation privately.

The host must enable share links and the service must allow creating them. Use the intended object key rather than a full storage URL or another service’s bucket. Creating a link does not itself upload or download the object.

Check what the link permits

A PUT to an existing object key can replace its current content. Choose a new intended path when receiving a new file, review versioning separately, and test with harmless data. Opening an upload link in a browser address bar does not upload a file; a browser GET is a different operation.

A link is not inherently single-use. Keep it out of public logs, tickets and screenshots. Choose an expiry suitable for the recipient’s task and share it through the intended private channel.

Diagnose an early refusal

A displayed expiry is an upper bound, not a promise of access until then. Key rotation, revoked access, service restrictions, changed object state or an altered hostname can make it fail earlier. Use the complete generated URL without rewriting its hostname or query.

Inspect the intended method, object path, expiry and current service state before generating repeated links.

See the PD Object Storage WHMCS guide for related tasks, or explore PD Object Storage.