Developers
SM.MS Compatibility
Migrate from SM.MS to S.EE with minimal code changes
S.EE supports SM.MS-compatible image uploads and upload history. Update the endpoint URLs as shown below.
Quick Migration
Replace the SM.MS API base URL with the S.EE equivalent:
| SM.MS | S.EE |
|---|---|
https://sm.ms/api/v2 | https://s.ee/api/v1/file |
Supported Endpoint
| SM.MS Endpoint | S.EE Endpoint | Description |
|---|---|---|
POST /api/v2/upload | POST /api/v1/file/upload | Upload image |
GET /api/v2/upload_history | GET /api/v1/files | Get upload history |
Upload Image
Request
curl -X POST "https://s.ee/api/v1/file/upload" \
-H "Authorization: your-api-key" \
-F "smfile=@/path/to/image.png" \
-F "domain=sm.ms" \
-F "custom_slug=my-image"Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
smfile | file | Yes | The image file to upload (alias: file) |
domain | string | No | Custom domain for the short link |
custom_slug | string | No | Custom slug for the URL (random if not provided) |
Response
{
"code": 200,
"data": {
"file_id": 14184137,
"width": 1024,
"height": 1024,
"filename": "my-cat.jpg",
"storename": "my-cat.jpg",
"size": 202814,
"path": "/2026/02/11/dm3K/my-cat.jpg",
"hash": "delete-hash-here",
"url": "https://i.see.you/2026/02/11/dm3K/my-cat.jpg",
"delete": "https://s.ee/api/v1/file/delete/delete-hash-here",
"page": "https://sm.ms/my-cat",
"upload_status": 2
},
"message": "success",
"success": true
}Upload History
Request
curl "https://s.ee/api/v1/files" \
-H "Authorization: your-api-key"Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
page | integer | No | Page number (default 1, 30 files per page) |
Response
{
"success": true,
"code": 200,
"message": "success",
"data": [
{
"file_id": 14186122,
"width": 1255,
"height": 636,
"filename": "chrome_O93NV9Z3G8.gif",
"storename": "chrome_O93NV9Z3G8.gif",
"size": 398517,
"path": "/2026/02/12/5isV/chrome_O93NV9Z3G8.gif",
"hash": "delete-hash-here",
"url": "https://i.see.you/2026/02/12/5isV/chrome_O93NV9Z3G8.gif",
"delete": "https://s.ee/api/v1/file/delete/delete-hash-here",
"page": "https://sm.ms/ZS3M",
"upload_status": 2,
"created_at": 1770908298
},
{
"file_id": 14186073,
"width": 1272,
"height": 644,
"filename": "firefox_P4lBSlG15y.gif",
"storename": "firefox_P4lBSlG15y.gif",
"size": 802256,
"path": "/2026/02/12/0Bmu/firefox_P4lBSlG15y.gif",
"hash": "delete-hash-here",
"url": "https://i.see.you/2026/02/12/0Bmu/firefox_P4lBSlG15y.gif",
"delete": "https://s.ee/api/v1/file/delete/delete-hash-here",
"page": "https://sm.ms/ATas",
"upload_status": 2,
"created_at": 1770904032
}
]
}Differences from SM.MS
While S.EE maintains compatibility with SM.MS API, there are some enhancements:
| Feature | SM.MS | S.EE |
|---|---|---|
| Custom domain | No | Yes |
| Custom slug | No | Yes |
| File size limit | 5MB | Varies by plan |
| Supported formats | Images only | Images, documents, and more |
Get Your API Key
To use the S.EE API, you need an API key:
- Sign up or log in at s.ee
- Go to Tools > API Token
- Generate a new API key
Need Help?
If you encounter any issues during migration, please contact support or check our API documentation.