How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Dropbox Sign (HelloSign) Team API

{'$ref': './markdown/en/tags/team-tag-description.md'}

Dropbox Sign (HelloSign) Team API is one of 13 APIs that Dropbox Sign (HelloSign) publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Team. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 10 operations across 9 paths, and defines 23 schemas. It is described by OpenAPI 3.2.0, at version 3.0.0.

Requests are made against a single base URL, https://api.hellosign.com/v3.

10 operations 9 paths 23 schemas 1 DELETE5 GET2 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.0.0
Base URL
https://api.hellosign.com/v3
Authentication
HTTP Basic, HTTP Bearer
License
Terms of Service
Resource Areas
1

Authentication & Security 2

Dropbox Sign (HelloSign) Team API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (api_key). It accepts HTTP bearer tokens (JWT) (oauth2). By default, every request must be authenticated.

  • api_key — Your API key can be used to make calls to the Dropbox Sign API. See [Authentication](/api/reference/authentication) for more information. ✅ Supported by Try it…
  • oauth2 — You can use an Access Token issued through an OAuth flow to send calls to the Dropbox Sign API from your app. The access scopes required by this endpoint are l…

Paths & Operations 10

Across 9 paths, the API surfaces 10 operations — 1 DELETE, 5 GET, 2 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Team 10

{'$ref': './markdown/en/tags/team-tag-description.md'}

PUT
/team/add_member
Add User to Team
teamAddMember 1 param body → 2004XX
POST
/team/create
Create Team
teamCreate body → 2004XX
DELETE
/team/destroy
Delete Team
teamDelete → 2004XX
GET
/team
Get Team
teamGet → 2004XX
PUT
/team
Update Team
teamUpdate body → 2004XX
GET
/team/info
Get Team Info
teamInfo 1 param → 2004XX
GET
/team/invites
List Team Invites
teamInvites 1 param → 2004XX
GET
/team/members/{team_id}
List Team Members
teamMembers 3 params → 2004XX
POST
/team/remove_member
Remove User from Team
teamRemoveMember body → 2014XX
GET
/team/sub_teams/{team_id}
List Sub Teams
teamSubTeams 3 params → 2004XX

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are AccountResponse (12 properties), AccountResponseQuotas (6 properties), TeamInviteResponse (6 properties), TeamInfoResponse (5 properties). Each schema is shown below with its type and property counts.

ErrorResponseError
object
Contains information about an error that occurred.
3 properties 2 required
TeamParentResponse
objectnull
Information about the parent team if a team has one, set to null otherwise.
2 properties
TeamResponse
object
Contains information about your team and its members
4 properties
TeamMemberResponse
object
3 properties
TeamAddMemberRequest
object
3 properties
TeamInfoResponse
object
5 properties
AccountResponse
object
12 properties
TeamInviteResponse
object
6 properties
TeamSubTeamsResponse
object
3 properties 2 required
AccountResponseUsage
object
Details concerning monthly usage
1 property
TeamInvitesResponse
object
2 properties 1 required
TeamUpdateRequest
object
1 property
SubTeamResponse
object
2 properties
TeamMembersResponse
object
3 properties 2 required
WarningResponse
object
A list of warnings.
2 properties 2 required
ListInfoResponse
object
Contains pagination information about the data returned.
4 properties
TeamRemoveMemberRequest
object
5 properties
TeamCreateRequest
object
1 property
AccountResponseQuotas
object
Details concerning remaining monthly quotas.
6 properties
ErrorResponse
object
1 property 1 required
TeamGetInfoResponse
object
2 properties 1 required
TeamGetResponse
object
2 properties 1 required
AccountResponseSettings
object
Subset of configured settings
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hellosign-team-api-openapi.yml Raw ↑

Other APIs Dropbox Sign (HelloSign) publishes across the network.

Dropbox Sign (HelloSign) Account API
Dropbox Sign (HelloSign) Api App API
Dropbox Sign (HelloSign) Bulk Send Job API
Dropbox Sign (HelloSign) Embedded API
Dropbox Sign (HelloSign) Fax API
Dropbox Sign (HelloSign) Fax Line API
Dropbox Sign (HelloSign) OAuth API
Dropbox Sign (HelloSign) Report API
Dropbox Sign (HelloSign) Signature Request API
Dropbox Sign (HelloSign) Template API
Dropbox Sign (HelloSign) Unclaimed Draft API
Dropbox Sign (HelloSign) Callbacks and Events API
Where this information came from

This is an independent, third-party profile of Dropbox Sign (HelloSign) Team API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.