Portals

A MASV Portal is a brandable file transfer web page hosted by MASV with a custom URL. End users can visit the page to upload files to MASV. After the sender has uploaded files, MASV notifies the specified email addresses associated with the Portal.

Custom expiry

Each Portal can override the default number of days that MASV stores an uploaded package with the custom_expiry_days property. Setting it to -1 specifies storage for an indefinite period if the Team’s plan allows it.

Extended Storage charges will be incurred beyond the free period included with the Team’s plan. For details, see How does Extended Storage Work and Pricing.

Regular and private access levels

A Portal’s access level can be regular or private. By default, all Portals are regular.

Packages received via a regular Portal can be viewed by all Team members, while packages uploaded to private Portals are accessible only for the Team members included in the Portal’s access list.

Creating a Portal

Method	Route
`POST`	`/v1/teams/{team_id}/portals`

Headers

Name	Type	Required	Description
`X-API-KEY`	String	Yes	API key
`Content-Type`	String	Yes	Must be `application/json`

Path parameters

Name	Type	Required	Description
`team_id`	String	Yes	The Team ID to bind the Portal to

Body

Name	Type	Required	Description
`name`	String	Yes	Name of the Portal
`subdomain`	String	Yes	Subdomain of the Portal
`message`	String	No	Message displayed on the Portal upload page
`has_access_code`	Boolean	No	Enable/disable access code
`access_code`	String	No	Access code for the Portal page
`active`	Boolean	No	Enable/disable Portal page. Default: `false`
`recipients`	String[]	No	Email(s) that will receive notifications
`has_download_password`	Boolean	No	Enable/disable download password. Default: `false`
`download_password`	String	No	Password to protect download access
`custom_expiry_days`	Integer	No	Storage days for packages. Range: `-1` to `65535`
`cloud_connections`	Object[]	No	Cloud connections attached to the Portal. See Cloud Connections
`custom_webhooks`	Object[]	No	Custom webhooks attached to the Portal. See Webhooks
`tag`	Object	No	Tag object for the Portal. See Tags
`access_level`	String	No	`regular` or `private`. Default: `regular`
`teamspace_id`	String	No	ID of the Teamspace to bind the Portal to
`terms_of_service_enabled`	Boolean	No	Enable/disable Terms of Service checkbox
`terms_of_service`	Object	No	Custom terms of service object
`package_size_restriction_enabled`	Boolean	No	Enable/disable package size restrictions
`max_package_size`	Integer	No	Maximum package size in bytes
`max_file_size`	Integer	No	Maximum individual file size in bytes
`max_file_count`	Integer	No	Maximum number of files
`file_type_restriction_enabled`	Boolean	No	Enable/disable file type restrictions
`file_types`	String[]	No	Allowed file extensions (e.g., `".mov"`, `".mp4"`)
`expiry_enabled`	Boolean	No	Enable/disable Portal expiry
`expiry`	String	No	Portal expiry date-time. Format: ISO 8601

Request

curl -d '{"name": "$NAME", "subdomain": "$SUBDOMAIN", "recipients": ["$R1_EMAIL"], "has_access_code": false, "active": true}' \
  -H "X-API-KEY: $API_KEY" \
  -H "Content-Type: application/json" \
  -X POST https://api.massive.app/v1/teams/$TEAM_ID/portals

Response

Returns 201 Created with the full Portal object.

Updating a Portal

Method	Route
`PUT`	`/v1/portals/{portal_id}`

Headers

Name	Type	Required	Description
`X-API-KEY`	String	Yes	API key
`Content-Type`	String	Yes	Must be `application/json`

Body

Same fields as creating a Portal. When updating, provide the full Portal object. A typical workflow: Get Portal → Modify Fields → Update Portal.

Request

curl -d '{"name": "$NAME", "subdomain": "$SUBDOMAIN", "active": true, "has_access_code": false}' \
  -H "X-API-KEY: $API_KEY" \
  -H "Content-Type: application/json" \
  -X PUT https://api.massive.app/v1/portals/$PORTAL_ID

Response

Returns 200 OK with the updated Portal object.

Fetching a Portal

Method	Route
`GET`	`/v1/portals/{portal_id}`

Headers

Name	Type	Required	Description
`X-API-KEY`	String	Yes	API key

Request

curl -H "X-API-KEY: $API_KEY" \
  -X GET https://api.massive.app/v1/portals/$PORTAL_ID

Response

Returns 200 OK with the Portal object.

Listing Portals

Method	Route
`GET`	`/v1.1/teams/{team_id}/portals`

Headers

Name	Type	Required	Description
`X-API-KEY`	String	Yes	API key
`Content-Type`	String	Yes	Must be `application/json`

Query parameters

Name	Type	Required	Description
`page`	Integer	No	Page number. Default: `1`
`limit`	Integer	No	Records per page, 1–50. Default: `50`
`sort`	String	No	Sort ascending (`fieldname`) or descending (`-fieldname`). Accepted: `name`, `created_at`, `active`
`name`	String	No	Substring match on Portal name
`subdomain`	String	No	Substring match on Portal subdomain
`tags`	String	No	Comma-separated tag IDs
`teamspaces`	String	No	Comma-separated Teamspace IDs

Request

curl -H "X-API-KEY: $API_KEY" \
  -X GET "https://api.massive.app/v1.1/teams/$TEAM_ID/portals?page=1&limit=10"

Response

Returns 200 OK with metadata.total and records array.

Listing Portal packages

Method	Route
`GET`	`/v1.1/portals/{portal_id}/packages`

Headers

Name	Type	Required	Description
`X-API-KEY`	String	Yes	API key
`Content-Type`	String	Yes	Must be `application/json`

Query parameters

Name	Type	Required	Description
`page`	Integer	No	Page number. Default: `1`
`limit`	Integer	No	Records per page, 1–50. Default: `50`
`sort`	String	No	Sort ascending or descending
`tags`	String	No	Comma-separated tag IDs
`sender`	String	No	Filter by sender email
`created_at_start`	String	No	Created after date (ISO 8601)
`created_at_end`	String	No	Created before date (ISO 8601)
`expiry_start`	String	No	Expires after date
`expiry_end`	String	No	Expires before date
`extra_storage`	Boolean	No	Filter by extra storage usage

Request

curl -H "X-API-KEY: $API_KEY" \
  -X GET "https://api.massive.app/v1.1/portals/$PORTAL_ID/packages?page=1&limit=3"

Response

Returns 200 OK with metadata.total and records array of package objects.