SDKs and Postman
Use this page when you want the fastest copy-paste path after Developer quickstart. Hilt publishes official public developer assets for the API:- TypeScript SDK
- Python SDK
- Postman collection
- Postman environment
- products
- hosted checkout
- payments
- Hilt Pay API
- agent bootstrap and setup intents
- rail settings and setup readiness
- payment sessions, proof submission, and entitlement checks
- memberships
- receipts
- support
- webhooks
Common questions
Does Hilt publish official SDKs?
Yes. Hilt publishes official TypeScript and Python SDKs, plus Postman assets for teams that want to inspect the API before writing code.Which SDK should I start with?
Use the TypeScript SDK for Node.js backends and frontend-adjacent tooling. Use the Python SDK for Python services, scripts, support automation, and data workflows.Is Postman still useful if I use an SDK?
Yes. Postman is the fastest way to inspect object shapes, test authentication, send webhook test events, and compare API behavior before putting the call into code.30-second SDK proof
If you only want to prove the published SDKs install and can talk to Hilt, use one of these smallest possible reads.TypeScript
Python
- the package installs cleanly
- auth works
- the SDK returns the same products your workspace sees in Hilt
Node .env.local
Python .env
TypeScript quickstart
Install
- npm:
https://www.npmjs.com/package/@hiltpay/sdk - GitHub:
https://github.com/Hiltpay/hilt-sdk-js
Copy-paste example
- one active product in Hilt
- one reusable
product.id - one reusable
slug - one buyer-facing checkout payload you can compare against the dashboard
Hilt Pay API durable entitlement check
checkEntitlement for durable or time-based access display and planning. For each metered request, use atomic consumption instead:
Hilt Pay API payment session
checkoutUrl for hosted Solana USDC checkout. Use paymentRequirement only when Hilt returns one for the protected-resource protocol path.
Settle an x402 V2 paid retry
When a buyer retries your protected resource withPAYMENT-SIGNATURE, settle it through Hilt before consuming the metered unit:
PAYMENT-RESPONSE to the buyer, atomically consume one unit with the same logical request id, and serve only after both operations succeed.
Hilt Pay API agent bootstrap
Python quickstart
Install
- PyPI:
https://pypi.org/project/hilt-sdk/ - GitHub:
https://github.com/Hiltpay/hilt-sdk-python
Copy-paste example
- one product created from Python
- one clean
product["id"] - one repeatable receipts query for later proof handling
Hilt Pay API durable entitlement check
check_entitlement for durable or time-based access display and planning. For metered work:
Hilt Pay API payment session
402 response or hosted checkout handoff.
Settle an x402 V2 paid retry
PAYMENT-RESPONSE, atomically consume one unit with the same logical request id, and serve only after both operations succeed.
Sandbox session helpers
Use sandbox sessions to validate SDK, webhook, receipt, and entitlement handling without live money. TypeScript:Webhook helpers
Both SDKs include raw-body verification helpers for Hilt webhooks. Hilt signs<timestamp>.<raw_json_body> and sends X-Hilt-Signature as t=<unix_timestamp>,v1=<hex_hmac_sha256>.
TypeScript:
Error handling
Both SDKs raiseHiltApiError for non-2xx API responses. The error includes:
codestatusCodeorstatus_coderequestIdorrequest_idretryabledocsUrlordocs_url- safe response body details
/developers/errors#payment-failed, /developers/errors#idempotency-in-progress, and /developers/errors#request-timeout.
TypeScript:
Subscription helper boundary
The SDKs expose the current public native subscription routes:- read a native subscription authorization
- create a cancellation intent
- confirm the signed cancellation
Hilt Pay API agent bootstrap
Postman quickstart
Use the public developer-assets repo for the mirrored machine-readable assets:https://github.com/Hiltpay/hilt-developer-assets
postman/hilt-postman-collection.jsonpostman/hilt-postman-environment.json
Set these environment variables
The shipped environment already includes these keys:baseUrlapiKeybearerTokenmerchantWalletproductIdslugpaymentIdpayApiAppIdpayApiProductIdmembershipIdreceiptIdendpointId
Run these requests in order
Products -> Create productHilt Pay API -> List Pay API railsHilt Pay API -> Create agent bootstrapHilt Pay API -> Submit setup manifestHilt Pay API -> Check setup readinessHilt Pay API -> Settle x402 V2 paymentHilt Pay API -> Consume metered entitlementHilt Pay API -> Check durable entitlementWebhooks -> Create webhook endpointWebhooks -> Send test eventTesting -> Create sandbox session
productIdslugendpointId- fake sandbox ids such as
fake_payment_idandfake_receipt_id
Why Postman is useful here
Postman is the fastest way to verify:- your auth surfaces are correct
- the public API matches the docs
- webhook endpoint management works with a bearer token
- sandbox responses match the object shapes your application expects
Contract and fallback assets
The supported public developer surface is represented by:- these developer docs
- the TypeScript SDK
- the Python SDK
- the Postman collection and environment
- approved snapshots in the developer-assets repo
- the
/v1/accessimplementation namespace solana_usdcas the first production settlement rail- x402 as the
402 Payment Requiredprotocol shape for protected-resource flows - scoped API keys for server and agent integrations
- receipt, entitlement, webhook, and audit retrieval through API
https://www.hilt.so/downloads/hilt-postman-collection-latest.jsonhttps://www.hilt.so/downloads/hilt-postman-environment-latest.json
https://www.hilt.so/downloads/hilt_sdk-1.2.0-py3-none-any.whl
Auth surfaces
For most merchant requests in the SDKs and Postman collection, use:What to do after the SDK quickstart
- run a signed test webhook event
- create one sandbox session
- check setup readiness before live traffic
- verify payment, membership, receipt, and delivery state afterwards

