Vanity aliases · OwnMediaHost Docs

Check the returned URL for your release.The platform README uses /a/… aliases and /private/… links; the API document uses /i/… and tokenized /f/… links. These supplied documents differ. Use the actual URL returned by your installed API instead of constructing it.

Aliases map human-readable paths to media files. A file with alias hero-banner becomes accessible at /i/hero-banner.

`GET /api/v1/aliases`

List all aliases.

Auth required: Yes

bash

curl -H "X-API-Key: YOUR_KEY" https://api.example.com/api/v1/aliases

Response:

json

{
  "success": true,
  "data": [
    {
      "id": "als_abc",
      "alias_path": "hero-banner",
      "media_id": "f_abc123",
      "media_public_id": "xK9mP2",
      "media_filename": "sunset-beach.jpg",
      "url": "/i/hero-banner",
      "created_at": "2026-09-19T14:00:00Z",
      "updated_at": "2026-09-19T14:00:00Z"
    }
  ]
}

`POST /api/v1/aliases`

Create a vanity alias for a media file.

Auth required: Yes

bash

curl -X POST https://api.example.com/api/v1/aliases \
  -H "X-API-Key: YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"alias_path": "company-logo", "media_id": "f_abc123"}'

`DELETE /api/v1/aliases/{id}`

Delete a vanity alias.

Auth required: Yes

bash

curl -X DELETE https://api.example.com/api/v1/aliases/als_abc \
  -H "X-API-Key: YOUR_KEY"