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

Avalanche Teleporter API

Find information about Teleporter transactions.

Avalanche Teleporter API is one of 25 APIs that Avalanche publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Teleporter. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and rate-limit docs.

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

Requests are made against a single base URL, https://data-api.avax.network.

3 operations 3 paths 23 schemas 3 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://glacier-api.avax.network/v1
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Avalanche Teleporter API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-glacier-api-key (apiKey). By default, every request must be authenticated, though some operations may also be called without credentials.

  • apiKey — Api keys provide higher access to rate limits. To obtain an api key, sign up for an account at https://build.avax.network/console/utilities/data-api-keys.

Paths & Operations 3

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

Teleporter 3

Find information about Teleporter transactions.

GET
/v1/teleporter/messages/{messageId}deprecated
[Deprecated] Gets a teleporter message by message ID. ⚠️ This operation will be removed in a future release. Please use /v1/icm/messages/:messageId endpoint instead .
getTeleporterMessage 1 param → 200400401403404429500502
GET
/v1/teleporter/messagesdeprecated
[Deprecated] Lists teleporter messages. Ordered by timestamp in descending order. ⚠️ This operation will be removed in a future release. Please use /v1/icm/messages endpoint instead .
listTeleporterMessages 8 params → 200400401403404429500502
GET
/v1/teleporter/addresses/{address}/messagesdeprecated
[Deprecated] Lists teleporter messages by address. Ordered by timestamp in descending order. ⚠️ This operation will be removed in a future release. Please use /v1/icm/addresses/:address/messages endp…
listTeleporterMessagesByAddress 4 params → 200400401403404429500502

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are DeliveredTeleporterMessage (17 properties), PendingTeleporterMessage (16 properties), DeliveredSourceNotIndexedTeleporterMessage (16 properties), DeliveredSourceNotIndexedIcmMessage (16 properties). Each schema is shown below with its type and property counts.

BadGateway
object
3 properties 3 required
ListTeleporterMessagesResponse
object
2 properties 1 required
IcmRewardDetails
object
8 properties 6 required
DeliveredTeleporterMessage
object
17 properties 16 required
DeliveredSourceNotIndexedIcmMessage
object
16 properties 15 required
DeliveredSourceNotIndexedTeleporterMessage
object
16 properties 15 required
TeleporterSourceTransaction
object
3 properties 3 required
Unauthorized
object
3 properties 3 required
ServiceUnavailable
object
3 properties 3 required
CurrencyCode
string
ISO 4217 currency code.
NotFound
object
3 properties 3 required
TooManyRequests
object
3 properties 3 required
BadRequest
object
3 properties 3 required
IcmReceipt
object
2 properties 2 required
Forbidden
object
3 properties 3 required
Network
string
PendingTeleporterMessage
object
16 properties 15 required
TeleporterReceipt
object
2 properties 2 required
TeleporterRewardDetails
object
8 properties 6 required
TeleporterDestinationTransaction
object
5 properties 5 required
Money
object
2 properties 2 required
InternalServerError
object
3 properties 3 required
IcmDestinationTransaction
object
5 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

avalanche-teleporter-api-openapi.yml Raw ↑

Other APIs Avalanche publishes across the network.

Avalanche Metrics API
Avalanche RPC API
Avalanche Webhooks API
Avalanche AVAX Supply API
Avalanche Data API Usage Metrics API
Avalanche EVM Balances API
Avalanche EVM Blocks API
Avalanche EVM Chains API
Avalanche EVM Contracts API
Avalanche EVM Transactions API
Avalanche Health Check API
Avalanche Interchain Messaging API
Where this information came from

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