Hevn Inc contracts API is one of 31 APIs that Hevn Inc publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include contracts. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes
34 operations
across 28 paths,
and defines 34 schemas.
It is described by OpenAPI 3.1.0, at version 0.1.2.
Requests are made against a single base URL, https://api.hevn.finance.
34 operations28 paths34 schemas2 DELETE10 GET4 PATCH16 POST2 PUT
Metadata
The identity and technical contract details declared by the specification.
Specification
OpenAPI 3.1.0
API Version
0.1.2
Base URL
https://api.hevn.finance/api/v1
Authentication
HTTP Bearer, API Key
Resource Areas
1
Authentication & Security 2
Hevn Inc contracts API declares
2 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (HTTPBearer).
An API key is passed in the header as x-api-key (ApiKeyAuth).
ApiKeyAuth — Alternative HEVN API key header. The CLI defaults to Authorization Bearer unless configured with HEVNAPIKEYHEADER=X-Api-Key.
Paths & Operations 34
Across 28 paths, the API surfaces 34 operations — 2 DELETE, 10 GET, 4 PATCH, 16 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.
The contract defines 34 schemas that model the data the API accepts and returns. The most detailed are ContractResponse (28 properties), ContractLastInvoice (20 properties), ContractorContractPreviewFields (18 properties), CreateContractRequest (16 properties). Each schema is shown below with its type and property counts.
TemplateDescriptor
object
Describes a document template and the fields a client must fill.
7 properties3 required
ValidationError
object
3 properties3 required
ServiceContractPreviewFields
object
9 properties9 required
UpdateContractLabelRequest
object
Request to update a contract label.
1 property
TemplateFieldSource
string
Where a template field's value comes from. USER — must be entered by the user. PROFILE — taken from a party's profile when available; if the profile is incompl…
Generate plain-text scope description from a role.
2 properties1 required
UpdateContractPaymentMethodsRequest
object
Payment methods selected by the contractor for this contract.
1 property
ApproveContractRequest
object
Optional body for contract approval — each party can provide their own data.
3 properties
GenerateContractDocumentResponse
object
6 properties3 required
ContractLastInvoice
object
Flat last invoice data embedded in contract responses.
20 properties7 required
ContractListResponse
object
List of contracts.
1 property1 required
TransactionType
string
Transaction type - payment rail. Includes all FiatPaymentType values (sepa/swift/ach/uaefts) plus extended fiat variants (wire/swift-usd/swift-eur/fedwire/pix)…
GenerateScopePrefillResponse
object
1 property1 required
ContractDocumentTemplateType
string
Markdown contract template type.
UpdateContractRequest
object
Request to update creator-owned contract terms and schedule.
6 properties
EmployerContractPreviewFields
object
14 properties14 required
CustomContractPreviewFields
object
1 property
UserAddress
object
Address schema for user. Canonical field names: streetaddress, addressline2, city, state, country, zip. Accepts legacy Align/IBAN field names (streetline1, str…
6 properties
ContractorContractPreviewFields
object
18 properties14 required
ContractType
string
Contract type.
PrepareContractDocumentRequest
object
Persist already prepared markdown as a document file.
4 properties2 required
TemplateFieldType
string
Structural type of a template field, so clients can render the right input. Composite types carry their shape: OBJECT populates :attr:TemplateField.fields, ARR…
Request to create a new contract. Exactly one of contractoremail or clientemail must be set. contractoremail — the creator is the client. clientemail — the cre…
16 properties
TemplateListResponse
object
List of fillable document templates.
1 property1 required
TemplateField
object
Single field of a document template, for dynamic discovery. Clients should prompt the user for USER fields, and for PROFILE fields only when the referenced par…
11 properties2 required
Specification
The full machine-readable OpenAPI contract behind this narrative.