layerhop (Python SDK)
Best-price cross-chain and same-chain swaps through one non-custodial API. Sync and async clients
on top of httpx, mirroring the TypeScript @layerhop/sdk.
The SDK never holds keys. It returns unsigned transactions. Your own wallet library (web3.py, eth-account, solders, a KMS, a hardware wallet…) signs and broadcasts them.
Install
pip install layerhop
Python 3.9+. The only runtime dependency is httpx.
Quickstart
Amounts are integer strings in base units (100 USDC = "100000000"), never floats.
from layerhop import LayerHop
lh = LayerHop(api_key="lh_live_...") # api_key is optional
# 1. Quote: every provider is asked; `best` pays the user the most.
q = lh.quote("base", "USDC", "100000000", "solana", "SOL",
sender="0xYourEvmAddress", recipient="YourSolanaAddress")
best = q["best"]
print(best["provider"], best["dstAmount"], best["estimatedSeconds"])
# 2. Build the unsigned transaction.
tx = lh.build_tx(best["quoteId"])
# 3. Sign and send with YOUR wallet library (example: web3.py on Base).
if tx["vm"] == "evm":
# if tx.get("approval"): send ERC-20 approve(spender, amount) on approval["token"] first
tx_hash = w3.eth.send_transaction({
"to": tx["to"], "data": tx["data"], "value": int(tx["value"]), "chainId": tx["chainId"],
}).hex()
else:
# Solana: tx["serializedTx"] is a base64 VersionedTransaction; sign it with solders.
# When tx.get("submitViaApi") is true, only sign, then: tx_hash = lh.submit(best["quoteId"], signed_b64)
...
# 4. Tell LayerHop you broadcast it (enables tracking, history and webhooks).
lh.report_submitted(best["quoteId"], tx_hash)
# 5. Track until filled / refunded / failed.
for s in lh.watch(best["provider"], tx_hash):
print(s["state"], s.get("dstTxHash"))
Async
from layerhop import AsyncLayerHop
async with AsyncLayerHop() as lh:
q = await lh.quote("base", "USDC", "100000000", "solana", "SOL", sender=s, recipient=r)
async for st in lh.watch("relay", tx_hash):
print(st["state"])
API
| Method | Endpoint |
|---|---|
health() |
GET /v1/health |
chains() |
GET /v1/chains |
tokens(chain) |
GET /v1/tokens?chain= |
quote(src_chain, src_token, amount, dst_chain, dst_token, *, sender, recipient, slippage_bps=50) |
GET /v1/quote |
build_tx(quote_id) |
POST /v1/orders → the tx |
simulate(quote_id) |
POST /v1/simulate (dry-run, records nothing) |
submit(quote_id, signed_transaction) |
POST /v1/orders/submit (Solana submitViaApi only) |
report_submitted(quote_id, tx_hash) |
POST /v1/orders/{quoteId}/submitted |
status(provider, id) |
GET /v1/orders/{provider}/{id} |
watch(provider, id, *, interval=3.0, timeout=1800) |
polls status, yields on change, stops when final |
stream_order(quote_id) |
GET /v1/orders/{quoteId}/events (SSE), yields the order until final |
list_orders(*, address, status, cursor, limit) |
GET /v1/orders |
checkout.create(amount, settle_chain, settle_token, recipient, *, merchant_name, description, reference, metadata, success_url, cancel_url, expires_in_minutes) |
POST /v1/checkout/sessions |
checkout.list(*, status, cursor, limit) |
GET /v1/checkout/sessions |
checkout.get(id) |
GET /v1/checkout/sessions/{id} (public) |
checkout.expire(id) |
POST /v1/checkout/sessions/{id}/expire |
checkout.quote(id, src_chain, src_token, *, sender, slippage_bps=None) |
POST /v1/checkout/sessions/{id}/quote (public) |
checkout.stream(id) |
GET /v1/checkout/sessions/{id}/events (SSE, public) |
checkout.products.create(name, amount, settle_chain, settle_token, recipient, *, description, merchant_name, success_url, cancel_url, expires_in_minutes, allowed_origins, active) |
POST /v1/checkout/products |
checkout.products.list(*, active, cursor, limit) |
GET /v1/checkout/products |
checkout.products.get(id) |
GET /v1/checkout/products/{id} (public) |
checkout.products.update(id, **fields) |
PATCH /v1/checkout/products/{id} (only the fields you pass) |
checkout.products.start_session(id, *, reference, metadata) |
POST /v1/checkout/products/{id}/sessions (public) |
checkout.refunds.create(session_id, *, amount, reason, from_, to) |
POST /v1/checkout/sessions/{id}/refunds |
checkout.refunds.list(session_id) |
GET /v1/checkout/sessions/{id}/refunds |
invoices.create(line_items, settle_chain, settle_token, recipient, *, customer_email, customer_name, merchant_name, memo, due_at, send) |
POST /v1/invoices |
invoices.list(*, status, cursor, limit) · invoices.get(id) · invoices.update(id, **fields) |
GET /v1/invoices · GET/PATCH /v1/invoices/{id} |
invoices.send(id) · invoices.void(id) |
POST /v1/invoices/{id}/send · /void |
invoices.public_view(id) · invoices.pay(id) |
GET /v1/invoices/{id}/public · POST /v1/invoices/{id}/pay (public) |
service_status() |
GET /v1/status (platform status, public) |
webhooks.stream() |
GET /v1/webhooks/stream (SSE, API key) |
webhooks.trigger(type) |
POST /v1/webhooks/trigger (test keys only) |
Client options: base_url (default https://api.layerhop.com), api_key (sent as x-api-key),
channel (default "api"), integrator, integrator_fee_bps, timeout, stream_timeout (read
timeout of streams; None, the default, waits forever), and http_client /
transport for custom httpx setups or tests.
Responses are plain dicts typed with TypedDict (keys keep the API's camelCase), so new fields
never break you.
Live order status
stream_order follows an order over Server-Sent Events instead of polling: it yields the order
now and on every change, and ends once it is final (filled, refunded, failed or expired).
checkout.stream(id) does the same for a checkout session (until paid, expired or
needs_review).
for order in lh.stream_order(best["quoteId"]):
print(order["status"], order.get("dstTxHash"))
# async
async for session in alh.checkout.stream(session_id):
print(session["status"])
The request is sent when iteration starts; break out of the loop to close the connection. A
missing order raises LayerHopApiError (ORDER_NOT_FOUND). Guide:
https://docs.layerhop.com/guides/live-status
Checkout (pay with any token)
Get paid in USDC or USDT on the chain you choose while the customer pays with any token on any
chain. Create a session with your API key and send the customer to its hosted url; the session
becomes paid (and a checkout.session.completed webhook fires) once the delivery is verified on
chain.
lh = LayerHop(api_key="lh_live_...")
session = lh.checkout.create("49000000", "base", "USDC", "0xYourPayoutAddress", # 49 USDC
description="Pro plan, 1 month", reference="order_1042",
success_url="https://shop.example.com/thanks")
print(session["url"]) # redirect the customer here
lh.checkout.get(session["id"])["status"] # open | processing | paid | expired | needs_review
lh.checkout.list(status="paid", limit=20)
lh.checkout.expire(session["id"]) # cancel an open session
Building your own payment page instead? get and quote are public (no key needed):
q = lh.checkout.quote(session_id, "arbitrum", "ETH", sender=payer_address)
best = q["best"] # best["srcAmount"] is what the payer sends; dstAmountMin >= amount due
tx = lh.build_tx(best["quoteId"])
# ... the payer's wallet signs and broadcasts tx ...
lh.report_submitted(best["quoteId"], tx_hash)
The async client has the same methods under await lh.checkout.…. Guide:
https://docs.layerhop.com/guides/checkout
Products and payment buttons
A product is a fixed price (amount, settlement token, payout address and redirect URLs) that
anyone may start a session from without being able to change it: the backing for payment
buttons, https://layerhop.com/buy/{id} links and store plugins. create, list and update
need your API key; get and start_session are public.
product = lh.checkout.products.create("Pro plan", "49000000", "base", "USDC", "0xYourPayoutAddress",
description="1 month", success_url="https://shop.example.com/thanks",
allowed_origins=["https://shop.example.com"])
print(product["url"]) # https://layerhop.com/buy/prod_...: share it or put it behind a button
lh.checkout.products.list(active=True)
lh.checkout.products.update(product["id"], active=False) # stops new sessions; only passed fields change
# Public (no key): start a session on the product's terms, adding only your order id.
session = LayerHop().checkout.products.start_session(product["id"], reference="order_1042")
print(session["url"], session["productId"])
update sends only the fields you pass; pass None to clear a nullable field such as
description. Guide: https://docs.layerhop.com/guides/payment-buttons
Invoices
Bill a customer by email for one or more line items; they pay with any token on the hosted page
https://layerhop.com/invoice/{id} and get a receipt (with a PDF) once it is paid. create, get,
list, update, send and void need an API key; public_view and pay are public.
inv = lh.invoices.create(
[{"description": "Design work (hours)", "quantity": 10, "unitAmount": "80000000"}], # 10 x 80 USDC
"base", "USDC", "0xYourPayoutAddress",
customer_email="ap@client.example", customer_name="Client Co", due_at="2026-11-01",
send=True, # finalize and email now (otherwise it stays a draft you can update)
)
print(inv["number"], inv["url"]) # INV-0001 https://layerhop.com/invoice/inv_...
lh.invoices.list(status="open")
lh.invoices.send(inv["id"]) # re-sends the email of an open invoice
lh.invoices.void(inv["id"]) # draft or open only
# Fulfil on the invoice.paid webhook. Statuses: draft, open, paid, void.
Refunds
Refunds are non-custodial: you sign them from your own wallet. create returns a quote that you
build, sign from quote["from"] (by default the session's payout address) and report; the refund
goes back to the payer's original chain and token (to="original", the default) or as the
settlement token (to="settlement"). Leave out amount to refund everything not yet refunded.
r = lh.checkout.refunds.create("cs_...", amount="10000000", reason="Partial refund")
tx = lh.build_tx(r["quote"]["quoteId"]) # sign and broadcast from r["quote"]["from"]
lh.report_submitted(r["quote"]["quoteId"], tx_hash)
lh.checkout.refunds.list("cs_...") # pending -> submitted -> completed (or failed)
# The session's refundedAmount grows and checkout.session.refunded is sent.
Platform status
lh.service_status() returns GET /v1/status, the data behind status.layerhop.com:
the overall status (operational, degraded or outage), each component with its 90-day uptime,
and the last 14 days of incidents. lh.status(provider, id) is still the provider order status.
Test mode
Use an lh_test_ key exactly like a live key: everything is served by the sandbox provider,
responses carry livemode: False, and built transactions have sandbox: True (never broadcast
them; report any hash with report_submitted). The last digits of amount pick the outcome:
…4001 refunds, …4002 fails, …4004 returns NO_ROUTE. Checkout sessions created with a
test key (cs_test_…) are paid through the sandbox too. See
https://docs.layerhop.com/guides/test-mode
Errors
Every non-2xx response raises LayerHopApiError with a stable code (QUOTE_EXPIRED,
NO_ROUTE, …), status, message and request_id. See
https://docs.layerhop.com/errors/<code>.
from layerhop import LayerHopApiError
try:
lh.build_tx(quote_id)
except LayerHopApiError as e:
if e.code == "QUOTE_EXPIRED":
... # re-quote
Webhooks
from layerhop import verify_webhook_signature, construct_webhook_event
# Flask example — use the RAW body
ok = verify_webhook_signature(secret, request.get_data(), request.headers.get("LayerHop-Signature"))
event = construct_webhook_event(secret, request.get_data(), request.headers.get("LayerHop-Signature"))
The header is t=<unix>,v1=<hex HMAC-SHA256(secret, "<t>.<body>")>. Signatures older or newer
than 300 s (tolerance) are rejected; comparison is constant-time.
Webhook tools
With an API key, webhooks.stream() yields your account's webhook events (in the key's live or
test mode) as they are created, with the exact payloads your endpoints receive. webhooks.trigger
creates a sample event in test mode (test keys only; a live key raises FORBIDDEN).
lh = LayerHop(api_key="lh_test_...")
r = lh.webhooks.trigger("order.filled") # {"eventId", "deliveries", "payload"}
for event in lh.webhooks.stream(): # runs until you break (or the server closes it)
print(event["type"], event["data"])
Development
python3 -m venv .venv && .venv/bin/pip install -e '.[dev]'
.venv/bin/python -m pytest
MIT licensed.
Metadata
Release files for layerhop 0.5.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| layerhop-0.5.1.tar.gz | 29.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| layerhop-0.5.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 51.1 kB
Release files / layerhop-0.5.1.tar.gz
| Download URL | layerhop-0.5.1.tar.gz |
|---|---|
| Size | 29.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e0df80a38bdc0dd27f23043e4ba37062caf0324b12b6c154063f8326e9990f64
|
|
BLAKE2b-256 checksum How to use checksums |
a6317f67543efd5fa8bca4f49c970e12d8b5b4358849e3dd5bad4cd6160c6483
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.2
|
Release files / layerhop-0.5.1-py3-none-any.whl
| Download URL | layerhop-0.5.1-py3-none-any.whl |
|---|---|
| Size | 21.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5f4b967c252addda32084ec4dacdcbfb5a1065ae800a8bf8584fb505aa97d973
|
|
BLAKE2b-256 checksum How to use checksums |
62db2361d98ce08cbb6636655eeb9b190fd282887a8e79503e5e40e2e911a289
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.2
|
Security for layerhop 0.5.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.