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

Enso layerzero API

The layerzero API from Enso — 4 operation(s) for layerzero.

Enso layerzero API is one of 9 APIs that Enso publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 4 operations across 4 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

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

4 operations 4 paths 8 schemas 4 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.enso.finance
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Enso layerzero API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (apiKey) (bearer). By default, every request must be authenticated.

Paths & Operations 4

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

layerzero 4
GET
/api/v1/layerzero/pool
Get LayerZero pool address for a token on a specific chain
LayerZeroController_getPoolAddress 4 params → 200
GET
/api/v1/stargate/pool
Get LayerZero pool address for a token on a specific chain
LayerZeroController_getPoolAddress 4 params → 200
GET
/api/v1/layerzero/bridge/check
Check bridge transaction status
LayerZeroController_checkBridgeTransaction 2 params → 200429
GET
/api/v1/stargate/bridge/check
Check bridge transaction status
LayerZeroController_checkBridgeTransaction 2 params → 200429

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are LayerZeroMessageStatus (13 properties), BridgeTransactionResponse (12 properties), BridgeHop (8 properties), EnsoEvent (8 properties). Each schema is shown below with its type and property counts.

LZPoolLookupResponse
object
6 properties 6 required
LayerZeroMessageStatus
object
13 properties 3 required
EnsoMetadata
object
5 properties
EnsoEvent
object
8 properties 4 required
LZDestinationTokenData
object
3 properties 3 required
BridgeHop
object
8 properties 3 required
BridgeTransactionResponse
object
12 properties 3 required
RefundDetails
object
4 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

enso-layerzero-api-openapi.yml Raw ↑

Other APIs Enso publishes across the network.

Enso ccip API
Enso cctp API
Enso metadata API
Enso projects API
Enso relay API
Enso shortcuts API
Enso standards API
Enso wallet API
Where this information came from

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