How It Works
IPFS Pinning Process
1. Upload your files to our IPFS gateway.
2. Files are pinned automatically to dedicated nodes.
3. A unique CID is generated for each file, ensuring content integrity.
4. Files are replicated across multiple nodes and regions for reliability.
API Example:
POST /v1/pinning/pins
Content-Type: application/json
Authorization: Bearer YOUR_API_KEY
{
"cid": "QmYourContentID",
"name": "MyFile"
}
Pre-signed URLs
1. Generate a pre-signed URL via API or dashboard.
2. Set the expiry time for secure, temporary access.
3. Share the URL with clients, apps, or users.
4. Access content securely without exposing API credentials.
API Example:
POST /v1/presigned-url
Content-Type: application/json
Authorization: Bearer YOUR_API_KEY
{
"cid": "QmYourContentID",
"expiry": 3600
}
Step-by-Step Workflow
1. Upload files to IPFS gateway → receive CID.
2. Pin the file for permanent storage.
3. Optionally generate pre-signed URLs for temporary access.
4. Share URLs with users or apps → content is accessible via gateway until expiry.
5. Monitor file usage, replication status, and analytics from the dashboard or API.
Frequently Asked Questions
1. What is a CID?
Ans: A Content Identifier (CID) is a unique hash representing your file on IPFS.
2. How long are pinned files stored?
Ans: Files remain stored permanently as long as they are pinned on our nodes.
3. Can I use pre-signed URLs with pinned files?
Ans: Yes, pre-signed URLs allow secure temporary access to your pinned files.
4. How do I integrate this into my application?
Ans: Use our REST API or SDKs to pin files, generate URLs, and monitor usage programmatically.
5. Is there global replication?
Ans: Yes, pinned files are replicated across multiple nodes and regions for high availability.
