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

Hilt Checkout API

The checkout API from Hilt — 12 operation(s) for checkout.

Hilt Checkout API is one of 21 APIs that Hilt publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Checkout. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and an AsyncAPI specification.

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

Requests are made against a single base URL, https://api.hilt.so.

12 operations 12 paths 24 schemas 12 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.hilt.so
Contact
Resource Areas
1

Paths & Operations 12

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

Checkout 12
POST
/v1/pay/broadcast
Record Payment Broadcast
record_payment_broadcast_v1_pay_broadcast_post body → 200422
POST
/v1/pay/automatic-renew/setup
Automatic Renew Setup
automatic_renew_setup_v1_pay_automatic_renew_setup_post body → 200422
POST
/v1/pay/identity/start
Start Checkout Identity Handshake
start_checkout_identity_handshake_v1_pay_identity_start_post body → 200422
POST
/v1/pay/identity/complete
Complete Checkout Identity Handshake
complete_checkout_identity_handshake_v1_pay_identity_complete_post body → 200422
POST
/v1/pay/phantom/connect/callback
Phantom Connect Callback
phantom_connect_callback_v1_pay_phantom_connect_callback_post body → 200422
POST
/v1/pay/phantom/message-url
Phantom Message Url
phantom_message_url_v1_pay_phantom_message_url_post body → 200422
POST
/v1/pay/phantom/renewal-message-url
Phantom Renewal Message Url
phantom_renewal_message_url_v1_pay_phantom_renewal_message_url_post body → 200422
POST
/v1/pay/phantom/message/callback
Phantom Message Callback
phantom_message_callback_v1_pay_phantom_message_callback_post body → 200422
POST
/v1/pay/phantom/renewal-message/callback
Phantom Renewal Message Callback
phantom_renewal_message_callback_v1_pay_phantom_renewal_message_callback_post body → 200422
POST
/v1/pay/phantom/transaction-url
Phantom Transaction Url
phantom_transaction_url_v1_pay_phantom_transaction_url_post body → 200422
POST
/v1/pay/phantom/transaction/callback
Phantom Transaction Callback
phantom_transaction_callback_v1_pay_phantom_transaction_callback_post body → 200422
POST
/v1/pay/confirm
Confirm Payment
confirm_payment_v1_pay_confirm_post body → 200422

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are ConfirmRequest (17 properties), ConfirmResponse (11 properties), IdentityHandshakeStartResponse (9 properties), IdentityHandshakeCompleteResponse (9 properties). Each schema is shown below with its type and property counts.

PhantomMessageCallbackResponse
object
4 properties 4 required
BroadcastResponse
object
3 properties 3 required
AutomaticRenewSetupResponse
object
5 properties 4 required
PhantomTransactionUrlRequest
object
3 properties 2 required
PhantomTransactionCallbackRequest
object
3 properties 3 required
PhantomMessageCallbackRequest
object
4 properties 4 required
PhantomConnectCallbackResponse
object
4 properties 4 required
ValidationError
object
5 properties 3 required
PhantomConnectCallbackRequest
object
4 properties 4 required
IdentityHandshakeCompleteResponse
object
9 properties 8 required
ConfirmResponse
object
11 properties 3 required
PhantomRenewalMessageCallbackResponse
object
4 properties 4 required
PhantomRenewalMessageUrlRequest
object
3 properties 2 required
ConfirmRequest
object
17 properties 2 required
IdentityHandshakeStartResponse
object
9 properties 8 required
PhantomTransactionCallbackResponse
object
3 properties 3 required
IdentityHandshakeCompleteRequest
object
3 properties 3 required
PhantomRenewalMessageCallbackRequest
object
4 properties 4 required
IdentityHandshakeStartRequest
object
6 properties 3 required
AutomaticRenewSetupRequest
object
1 property 1 required
PhantomMessageUrlRequest
object
3 properties 2 required
HTTPValidationError
object
1 property
PhantomDeeplinkResponse
object
2 properties 2 required
BroadcastRequest
object
4 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hilt-so-checkout-api-openapi.yml Raw ↑

Other APIs Hilt publishes across the network.

Hilt Pay Agent Gateway (MCP + A2A)
Hilt PayMe MCP Connector
Hilt Account API
Hilt Agent Commerce API
Hilt API Keys API
Hilt Auth API
Hilt Billing API
Hilt Checkout Domains API
Hilt Hilt Pay API
Hilt Hilt PayMe Connector API
Hilt Integrations API
Hilt Memberships API
Where this information came from

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