Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion api-reference/endpoint/ipfs/pin-file-to-ipfs.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -113,7 +113,7 @@ await uploadBase64("SGVsbG8gZnJvbSBQaW5hdGEhIDop");

<Accordion title="Folders">

Folders can also be uploaded via the API by creating an array of files and mapping over them to add them to the form data. This is different then having a single `file` entry and having multiple files for that one entry, which does not work.
Folders can also be uploaded via the API by creating an array of files and mapping over them to add them to the form data. This is different than having a single `file` entry and having multiple files for that one entry, which does not work.

<CodeGroup>

Expand Down
2 changes: 1 addition & 1 deletion files/uploading-files.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -369,7 +369,7 @@ The profile a file was uploaded with is returned as `cid_version` on the file's

### Client Side Uploads

There are situations where you may need to upload a file client side instead of server side. A great example is in Next.js where there is a 4MB file size restriction for files passed through Next's API routes. To solve this you can create a signed upload URL on the server and then pass it to the client for it to be consumed. This way your admin API key stays safe behind a server. Creating signed upload URLs can be done with either the [SDK](/sdk/upload/public/create-signed-url) or the [API](/api-reference/endpoint/create-signed-upload-url), and you can designate how long the URL is valid for or if there is other infromation you want to include such as metadata or a group ID.
There are situations where you may need to upload a file client side instead of server side. A great example is in Next.js where there is a 4MB file size restriction for files passed through Next's API routes. To solve this you can create a signed upload URL on the server and then pass it to the client for it to be consumed. This way your admin API key stays safe behind a server. Creating signed upload URLs can be done with either the [SDK](/sdk/upload/public/create-signed-url) or the [API](/api-reference/endpoint/create-signed-upload-url), and you can designate how long the URL is valid for or if there is other information you want to include such as metadata or a group ID.

Setting up a server side API endpoint might look something like this:

Expand Down