Developer tools for link management, text sharing, and file sharing.
S.EE provides short links, custom domains, QR codes, link analytics, link-in-bio pages, and secure text and file sharing. This organization is the official home of our SDKs, command-line tools, integrations, and documentation.
Get started · API reference · SDK guide · All repositories · Service status
The S.EE REST API supports short URLs, shared text, file uploads, custom domains, and analytics.
- Base URL:
https://s.ee/api/v1 - Authentication:
Authorization: Bearer YOUR_ACCESS_TOKEN - Prerequisites: An S.EE account with an active plan and an API access token
Start with the developer guide for authentication and request examples, or browse the complete API reference. Never commit API tokens to source control; use environment variables or your platform's secret manager.
| Language | Repository | Installation | Support Priority |
|---|---|---|---|
| TypeScript / JavaScript | sdotee/sdk.ts | npm install see-sdk |
A |
| Go | sdotee/sdk.go | go get github.com/sdotee/sdk.go |
A |
| Python | sdotee/sdk.py | pip install see-sdk |
A |
| Rust | sdotee/sdk.rs | cargo add see-sdk |
B |
| Swift | sdotee/sdk.swift | Swift Package Manager | B |
| Java | sdotee/sdk.java | dev.s.ee:see-java-sdk |
B |
| PHP | sdotee/sdk.php | composer require sdotee/sdk |
C |
| .NET / C# | sdotee/sdk.cs | - | C |
| sdotee/sdk.zig | Build from source | - |
Feature coverage and runtime requirements differ by SDK. Check the repository README and latest release before choosing a version for production use.
Contributions to our SDKs, tools, and documentation are welcome.
- Open bugs in the repository that owns the affected code.
- Check that repository's README and contribution guide for setup, style, and test commands.
- Keep pull requests focused and include tests or documentation for behavior changes.
- Propose cross-project features in GitHub Discussions.
Each project publishes its own support policy, release history, and license. Unless stated otherwise in a repository, do not assume identical API coverage or release cadence across SDKs.
- General support: hi@s.ee
- Developer questions: dev@s.ee
- Service availability: status.s.ee
- Product security and anti-abuse: Security documentation
To report a vulnerability, do not open a public issue or discussion. Email hi@s.ee with the affected project or endpoint, reproduction steps, and potential impact. Please avoid including real user data, credentials, or access tokens.