drophost
drophost HTTP API
- Authorization: Bearer dh_…
- multipart/form-data for publishes
- 60 requests per minute per key
POST /api/v1/publish
Send multipart/form-data with a file field. Optional kind is file (default) or site. Optional slug sets the subdomain on a new project. Optional projectId attaches to a project you already own. The response includes id, slug, url, and files. Filename clashes return FILE_EXISTS.
GET /api/v1/projects
Lists projects you own: id, name, slug, and url. Use an id as projectId when publishing into an existing project.
HTTP publish alongside MCP
Use the drophost HTTP API when you need uploads beyond the MCP oneshot 4 MB cap or prefer plain REST from scripts. The same hashed API key authenticates requests. Published projects appear in the dashboard like browser uploads, and recipients open the resulting link without creating an account.
Plan quotas for API publishes
drophost API publishes consume plan storage and project slots: Free one project / 2 MB, Starter 8 / 100 MB at €5/mo, Pro 30 / 500 MB at €12/mo. Links stay until deleted; replace a file to keep the URL. Recipients still need no account to download or view the content.
Common questions
How do I publish a file with the HTTP API?
POST /api/v1/publish on drophost as multipart/form-data with a file field and Authorization: Bearer. Optional kind, slug, and projectId fields.
How do I list my projects?
GET /api/v1/projects on drophost with the same Bearer key. Use a returned id as projectId on the next publish.
Is there a rate limit?
Yes. drophost limits API keys to 60 requests per minute. 429 responses include Retry-After.
Related
Ready to publish?
Drop a file on the homepage and get a live drophost URL in seconds.