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

Xquik Guest Wallets API

Accountless prepaid access for paid read endpoints

Xquik Guest Wallets API is one of 22 APIs that Xquik publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Guest Wallets. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 3 operations across 3 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://xquik.com.

3 operations 3 paths 8 schemas 1 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://xquik.com/api/v1
Authentication
API Key, HTTP Bearer, API Key
Contact
Resource Areas
1

Authentication & Security 3

Xquik Guest Wallets API declares 3 security schemes for authenticating requests. An API key is passed in the header as x-api-key (apiKey). It accepts HTTP bearer tokens (oauthBearer). An API key is passed in the cookie as __Host-xquik_session (cookieSession). By default, every request must be authenticated.

  • apiKey — Xquik API key passed through the x-api-key header. Xquik-Api-Key is a vendor-prefixed alias. API keys beginning with xq can also use Authorization: Bearer.
  • oauthBearer — OAuth 2.1 access token passed through Authorization: Bearer. Values beginning with xq remain Xquik API-key credentials, not OAuth tokens.
  • cookieSession — Secure Xquik browser session cookie.

Paths & Operations 3

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

Guest Wallets 3

Accountless prepaid access for paid read endpoints

POST
/api/v1/guest-wallets
Create an accountless prepaid wallet checkout
createGuestWallet 1 param body → 201400409410413415423429
POST
/api/v1/guest-wallets/topups
Create another guest wallet checkout
topUpGuestWallet 1 param body → 201400401409410413415423
GET
/api/v1/guest-wallets/status
Get guest wallet and payment status
getGuestWalletStatus → 200401429default

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are GuestWalletCheckoutResponse (15 properties), GuestWalletStatusResponse (8 properties), GuestWalletPurchaseStatus (6 properties), Error (5 properties). Each schema is shown below with its type and property counts.

GuestWalletCheckoutResponse
object
Pending Stripe checkout and guest wallet purchase details.
15 properties 12 required
GuestWalletStatusResponse
object
Current balance, usability, and latest guest purchase state.
8 properties 8 required
GuestWalletTopupResponse
Existing guest wallet top-up response without a new key.
GuestWalletAmount
object
Confirmed USD amount for a guest wallet purchase.
2 properties 2 required
GuestWalletPurchaseStatus
object
Latest guest wallet purchase fulfillment state.
6 properties 6 required
GuestWalletCreateResponse
Initial guest wallet response containing the one-time key.
Error
object
Error response. Default v1 returns a legacy string error code. Send xquik-api-contract: 2026-04-29 to receive the structured best-practice error object.
5 properties 1 required
GuestWalletPurchaseRequest
object
User-confirmed guest wallet checkout request.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

xquik-api-guest-wallets-api-openapi.yml Raw ↑

Other APIs Xquik publishes across the network.

Xquik API MCP Server
Xquik Docs MCP Server
Xquik Account API
Xquik API Keys API
Xquik Articles API
Xquik Communities API
Xquik Composition API
Xquik Draws API
Xquik Events API
Xquik Extractions API
Xquik Lists API
Xquik Media API
Where this information came from

This is an independent, third-party profile of Xquik Guest Wallets 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.