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

Hevn Inc tee API

The tee API from Hevn Inc — 3 operation(s) for tee.

Hevn Inc tee 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 TEE. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 3 operations across 3 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 0.1.2.

Requests are made against a single base URL, https://api.hevn.finance.

3 operations 3 paths 6 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.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 tee 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 3

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

tee 3
POST
/api/v1/auth/tee/attestate_jwt
Attestate Jwt
attestate_jwt_api_v1_auth_tee_attestate_jwt_post body → 200422
GET
/api/v1/auth/tee/encryption_key
Get Encryption Key
get_encryption_key_api_v1_auth_tee_encryption_key_get → 200
GET
/api/v1/auth/tee/google_certs
Get Google Certs
get_google_certs_api_v1_auth_tee_google_certs_get → 200

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are app__routers__security__tee__AttestateJwtResponse (5 properties), GoogleCertsResponse (3 properties), ValidationError (3 properties), app__routers__security__tee__AttestateJwtRequest (2 properties). Each schema is shown below with its type and property counts.

HTTPValidationError
object
1 property
EncryptionKeyResponse
object
1 property 1 required
ValidationError
object
3 properties 3 required
app__routers__security__tee__AttestateJwtResponse
object
5 properties 5 required
app__routers__security__tee__AttestateJwtRequest
object
2 properties 2 required
GoogleCertsResponse
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hevn-inc-tee-api-openapi.yml Raw ↑

Other APIs Hevn Inc publishes across the network.

Hevn Inc 2FA API
Hevn Inc Activity API
Hevn Inc apps API
Hevn Inc apps-transfer API
Hevn Inc auth API
Hevn Inc B2B API
Hevn Inc Balance API
Hevn Inc Banks API
Hevn Inc Cards API
Hevn Inc Chat API
Hevn Inc contracts API
Hevn Inc Devices API
Where this information came from

This is an independent, third-party profile of Hevn Inc tee 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.