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

Lightspark Contact Verification API

Endpoints for verifying a customer's email and phone via one-time codes. Required only for customers whose payment provider mandates contact verification (e.g. EU customers); other providers return 409.

Lightspark Contact Verification API is one of 22 APIs that Lightspark publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Contact Verification. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 4 operations across 4 paths, and defines 10 schemas. It is described by OpenAPI 3.1.0, at version 2025-10-13.

Requests are made against a single base URL, https://api.lightspark.com/grid/2025-10-13.

4 operations 4 paths 10 schemas 4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
2025-10-13
Base URL
https://api.lightspark.com/grid/2025-10-13
Authentication
HTTP Basic, HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 3

Lightspark Contact Verification API declares 3 security schemes for authenticating requests. It accepts HTTP basic authentication (BasicAuth). It accepts HTTP bearer tokens (AgentAuth). An API key is passed in the header as X-Grid-Signature (WebhookSignature). By default, every request must be authenticated.

  • BasicAuth — API token authentication using format :
  • AgentAuth — Bearer token authentication for agent-scoped endpoints. The token is the accessToken returned when redeeming a device code via POST /agents/device-codes/{code}…
  • WebhookSignature — Secp256r1 (P-256) asymmetric signature of the webhook payload, which can be used to verify that the webhook was sent by Grid. To verify the signature: 1. Get t…

Paths & Operations 4

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

Contact Verification 4

Endpoints for verifying a customer's email and phone via one-time codes. Required only for customers whose payment provider mandates contact verification (e.g. EU customers); othe…

POST
/customers/{customerId}/verify-email
Send an email verification code to a customer
sendCustomerEmailVerification 1 param → 204401404409500
POST
/customers/{customerId}/verify-email/confirm
Confirm a customer's email verification code
confirmCustomerEmailVerification 1 param body → 200400401404409500
POST
/customers/{customerId}/verify-phone
Send a phone verification code to a customer
sendCustomerPhoneVerification 1 param → 204401404409500
POST
/customers/{customerId}/verify-phone/confirm
Confirm a customer's phone verification code
confirmCustomerPhoneVerification 1 param body → 200400401404409500

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are Customer (12 properties), Error401 (4 properties), Error400 (4 properties), Error500 (4 properties). Each schema is shown below with its type and property counts.

Error400
object
4 properties 3 required
ContactVerification
object
Email and/or phone verification state for the customer. This object is only present when the customer's regulatory jurisdiction requires contact verification (…
2 properties
Customer
object
12 properties 3 required
Error409
object
4 properties 3 required
CustomerType
string
Whether the customer is an individual or a business entity
Error500
object
4 properties 3 required
ContactVerificationConfirmRequest
object
Request body for confirming an email or phone verification challenge.
1 property 1 required
ContactVerificationStatus
string
Status of an individual contact-verification channel (email or phone). PENDING means verification is required but not yet completed; VERIFIED means the channel…
Error401
object
4 properties 3 required
Error404
object
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lightspark-contact-verification-api-openapi.yml Raw ↑

Other APIs Lightspark publishes across the network.

Lightspark Agent Management API
Lightspark Agent Operations API
Lightspark API Tokens API
Lightspark Available UMA Providers API
Lightspark Cards API
Lightspark Cross-Currency Transfers API
Lightspark Customers API
Lightspark Discoveries API
Lightspark Documents API
Lightspark Embedded Wallet Auth API
Lightspark Exchange Rates API
Lightspark External Accounts API
Where this information came from

This is an independent, third-party profile of Lightspark Contact Verification 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.