POST

v1: Create a directory

https://www.helprange.com/public-api/directory

Creates a folder in your team. Both properties must be present; onlyIpAddresses may be null.

Plans: Max, Unlimited, Deal Room Pass, trial. Auth: the API key in Authorization (bare, or Bearer hr_live_…) (v1). Scope: documents:write. Operation id: v1CreateDirectory

Request body

Content types: application/json.

FieldTypeDescription
name requiredstringFolder name (unique in the team).
onlyIpAddresses requiredstring or nullComma-separated IP addresses / CIDR ranges allowed to view, or null.

Example request

curl -X POST https://www.helprange.com/public-api/directory \
  -H "Authorization: $HELPRANGE_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-binary '{"name": "my directory", "onlyIpAddresses": "34.124.145.56,101.127.144.90"}'

The samples read the key from the HELPRANGE_API_KEY environment variable.

Responses

StatusDescription
200OK
400Invalid input – the message says which parameter.
401Missing or invalid API key / OAuth token. Team keys: code invalid_key, key_revoked, key_expired or key_owner_removed.
402Your plan does not include the REST API (or this feature).
403v1: the key is invalid, or the folder / file / guest / data room is not yours (HTML page unless you send Accept: application/json). Team keys (v1 and v2): code insufficient_scope with required_scope – the key lacks the scope this endpoint needs.
429A usage limit was reached – wait Retry-After seconds.
Example response · 200
{
  "id": 260,
  "link": "/view-directory/8956d1e7b91b47e196a8040b1d4894f8"
}

Try it

Uses your real account. The request goes from your browser straight to www.helprange.com with your API key and acts as you – this POST changes data. The key stays in this page (in this tab's session storage only if you tick the box), is never put in a URL and is not sent to analytics. Do not paste a key on a shared computer.