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

Eclipse HelloSign API

REST API wrapping Dropbox Sign (HelloSign) for Eclipse Foundation document signing — signature requests for committer paperwork, membership and working-group agreements — plus the inbound signature event callback.

Eclipse HelloSign API is one of 26 APIs that Eclipse Foundation publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Documents, Foundation, Signatures, and Webhooks. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 6 operations across 5 paths, organized into 2 resource areas, and defines 5 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against a single base URL, https://api.eclipse.org/foundation/hellosign.

6 operations 5 paths 5 schemas 4 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://api.eclipse.org/foundation/hellosign
Authentication
OpenID Connect
Resource Areas
2

Authentication & Security 1

Eclipse HelloSign API declares 1 security scheme for authenticating requests. It supports OpenID Connect (openId) discovered at https://auth.eclipse.org/auth/realms/document-signature/.well-known/openid-configuration.

Paths & Operations 6

Across 5 paths, the API surfaces 6 operations — 4 GET, 2 POST. They span 2 resource areas: Hellosign Signature Request, Hellosign Event Callbacks. Each is listed below with its method, path, parameters, and response codes.

Hellosign Signature Request 5
GET
/
Hellosign signature list
getAllHellosignRequests → 200403500
POST
/
Create Hellosign signature
createNewHellosignRequests body → 200400403500
GET
/{id}
Hellosign signature
getHellosignRequestById 1 param → 200403404500
GET
/{id}/document
Hellosign signature document
getHellosignRequestDocumentById 1 param → 200403404500
GET
/templates
Document signature templates
getTemplates → 200401
Hellosign Event Callbacks 1
POST
/callback
Hellosign Events callback
hellosignRequestEventsCallback → 200404500

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are EfHellosignRequest (9 properties), HellosignSignatureRequest (4 properties), EfTemplateDocument (3 properties). Each schema is shown below with its type and property counts.

EfHellosignRequest
object
9 properties 9 required
EfHellosignRequests
array
HellosignSignatureRequest
object
4 properties 2 required
EfSignatureTemplates
array
EfTemplateDocument
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

eclipse-hellosign-api-openapi.yml Raw ↑

Other APIs Eclipse Foundation publishes across the network.

Eclipse Marketplace API
Eclipse Foundation Web API
Eclipse Projects API
Open VSX Registry API
Eclipse Newsroom REST API
Eclipse Foundation Eclipse Marketplace REST API API
Eclipse Foundation Favorites API
Eclipse Foundation Featured API
Eclipse Foundation Node API
Eclipse Foundation Popular API
Eclipse Foundation Recent API
Eclipse Foundation Search API
Where this information came from

This is an independent, third-party profile of Eclipse HelloSign 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.