@coinbase/cdp-sdk 1.51.1 → 1.51.2

package/src/openapi-client/generated/end-user-account-management/end-user-account-management.ts

@@ -100,6 +100,9 @@ export const getEndUser = (
   Both params must be provided together.
 
 - **phoneNumber**: looks up a user by their SMS-verified phone number.
+- **siweAddress**: looks up a user by the Ethereum address they authenticated
+  with via Sign In With Ethereum (EIP-4361).
+
 
 Returns all matching end users. If no end users match, an empty array is returned.
 

package/src/openapi-client/generated/onramp/onramp.ts

@@ -9,17 +9,65 @@ import type {
   CreateOnrampOrder201,
   CreateOnrampOrderBody,
   CreateOnrampSession201,
-  CreateOnrampSessionBody,
   GetOnrampOrderById200,
   GetOnrampUserLimits200,
   GetOnrampUserLimitsBody,
+  InitiateOnrampVerificationRequest,
   OnrampLimitUpgradeRequest,
+  OnrampSessionRequest,
+  OnrampVerificationConfirmation,
+  OnrampVerificationId,
+  OnrampVerificationInitiation,
+  SubmitOnrampVerificationRequest,
 } from "../coinbaseDeveloperPlatformAPIs.schemas.js";
 
 import { cdpApiClient } from "../../cdpApiClient.js";
 
 type SecondParameter<T extends (...args: never) => unknown> = Parameters<T>[1];
 
+/**
+ * Initiates OTP verification by sending a 6-digit code to the user via the specified channel (SMS or email). Returns a `verificationId` that must be passed to the Submit Onramp Verification endpoint along with the OTP code within 10 minutes.
+
+**Access to this API requires allowlisting.** During Onramp Headless API onboarding, contact the Onramp team to enable Onramp-managed verification for your application.
+ * @summary Initiate onramp verification
+ */
+export const initiateOnrampVerification = (
+  initiateOnrampVerificationRequest: InitiateOnrampVerificationRequest,
+  options?: SecondParameter<typeof cdpApiClient<OnrampVerificationInitiation>>,
+) => {
+  return cdpApiClient<OnrampVerificationInitiation>(
+    {
+      url: `/v2/onramp/verifications`,
+      method: "POST",
+      headers: { "Content-Type": "application/json" },
+      data: initiateOnrampVerificationRequest,
+    },
+    options,
+  );
+};
+/**
+ * Submits the OTP code to complete verification. On success, marks the verification as verified and returns the same `verificationId`. The destination does not need to be re-sent. Onramp uses the value captured at initiation time.
+
+The returned `verificationId` should be stored on the user's device and passed to the Create Onramp Order endpoint. It is valid for 60 days.
+
+**Access to this API requires allowlisting.** During Onramp Headless API onboarding, contact the Onramp team to enable Onramp-managed verification for your application.
+ * @summary Submit onramp verification
+ */
+export const submitOnrampVerification = (
+  verificationId: OnrampVerificationId,
+  submitOnrampVerificationRequest: SubmitOnrampVerificationRequest,
+  options?: SecondParameter<typeof cdpApiClient<OnrampVerificationConfirmation>>,
+) => {
+  return cdpApiClient<OnrampVerificationConfirmation>(
+    {
+      url: `/v2/onramp/verifications/${verificationId}/submit`,
+      method: "POST",
+      headers: { "Content-Type": "application/json" },
+      data: submitOnrampVerificationRequest,
+    },
+    options,
+  );
+};
 /**
  * Create a new Onramp order or get a quote for an Onramp order. Either `paymentAmount` or `purchaseAmount` must be provided.
 
@@ -77,7 +125,7 @@ export const getOnrampOrderById = (
  * @summary Create an onramp session
  */
 export const createOnrampSession = (
-  createOnrampSessionBody: CreateOnrampSessionBody,
+  onrampSessionRequest: OnrampSessionRequest,
   options?: SecondParameter<typeof cdpApiClient<CreateOnrampSession201>>,
 ) => {
   return cdpApiClient<CreateOnrampSession201>(
@@ -85,7 +133,7 @@ export const createOnrampSession = (
       url: `/v2/onramp/sessions`,
       method: "POST",
       headers: { "Content-Type": "application/json" },
-      data: createOnrampSessionBody,
+      data: onrampSessionRequest,
     },
     options,
   );
@@ -136,6 +184,12 @@ export const requestLimitsUpgrade = (
     options,
   );
 };
+export type InitiateOnrampVerificationResult = NonNullable<
+  Awaited<ReturnType<typeof initiateOnrampVerification>>
+>;
+export type SubmitOnrampVerificationResult = NonNullable<
+  Awaited<ReturnType<typeof submitOnrampVerification>>
+>;
 export type CreateOnrampOrderResult = NonNullable<Awaited<ReturnType<typeof createOnrampOrder>>>;
 export type GetOnrampOrderByIdResult = NonNullable<Awaited<ReturnType<typeof getOnrampOrderById>>>;
 export type CreateOnrampSessionResult = NonNullable<

package/src/openapi-client/generated/sql-api/sql-api.ts

@@ -30,21 +30,34 @@ Queries are executed against optimized data structures for high-performance anal
   - No DDL or DML operations
   - Query that follow limits (defined below)
 
-### Supported Tables
-
-  - `<network>.events` - Base mainnet decoded event logs with parameters, event signature, topics, and more.
-  - `<network>.transactions` - Base mainnet transaction data including hash, block number, gas usage.
-  - `<network>.blocks` - Base mainnet block information.
-  - `<network>.encoded_logs` - Encoded log data of event logs that aren't able to be decoded by our event decoder (ex: log0 opcode).
-  - `<network>.decoded_user_operations` - Decoded user operations data including hash, block number, gas usage, builder codes, entrypoint version, and more.
-  - `<network>.transaction_attributions` - Information about the attributions of a transaction to a builder and associated builder codes.
-
 ### Supported Networks
 
   - Base Mainnet: `base`
   - Base Sepolia: `base_sepolia`
+  - Solana Mainnet: `solana`
+  - Hyperevm Mainnet: `hyperevm`
+
+### Supported Tables
+
+The below tables are supported for `base` and `base_sepolia` networks.
+
+  | Table | Description |
+  | --- | --- |
+  | `<network>.events` | Decoded event logs with parameters, event signature, topics, and more. |
+  | `<network>.transactions` | Transaction data including hash, block number, and gas usage. |
+  | `<network>.blocks` | Block information. |
+  | `<network>.encoded_logs` | Encoded log data for event logs that cannot be decoded by our event decoder (ex: log0 opcode). |
+  | `<network>.decoded_user_operations` | Decoded user operations data including hash, block number, gas usage, builder codes, entrypoint version, and more. |
+  | `<network>.transaction_attributions` | Information about the attributions of a transaction to a builder and associated builder codes. |
+
+  Following the above, the valid tables on Base Mainnet are `base.events`, `base.transactions`, `base.blocks`, `base.encoded_logs`, `base.decoded_user_operations`, and `base.transaction_attributions`.
+
+Separately, there is a limited set of tables supported for `solana` and `hyperevm` networks:
 
-  So for example, valid tables are: `base.events`, `base_sepolia.events`, `base.transactions`, etc.
+  | Table | Description |
+  | --- | --- |
+  | `solana.instructions` | Solana instruction call data including program ID, instruction data, and more. Currently supports just Token2022 and SPL Token programs. |
+  | `hyperevm.events` | Hyperevm decoded event logs with parameters, event signature, topics, and more. Currently supports just B20 events. |
 
 ### Query Limits
 

package/src/openapi-client/generated/webhooks/webhooks.ts

@@ -41,58 +41,30 @@ export const listWebhookSubscriptions = (
   );
 };
 /**
- * Subscribe to real-time events across CDP products using flexible filtering.
+ * Subscribe to real-time events across CDP products.
 
-### Event Types
-
-**Onchain Events** - Monitor Base mainnet with microsecond precision:
-- `onchain.activity.detected` - Smart contract events, transfers, swaps, NFT activity
-- **Requires** `labels` for filtering (e.g., `contract_address`, `event_name`)
+### Filtering
 
-**Onramp/Offramp Events** - Transaction lifecycle notifications:
-- `onramp.transaction.created`, `onramp.transaction.updated`
-- `onramp.transaction.success`, `onramp.transaction.failed`
-- `offramp.transaction.created`, `offramp.transaction.updated`
-- `offramp.transaction.success`, `offramp.transaction.failed`
-- **No labels required** - maximum simplicity for transaction monitoring
+Onchain events can utilize multi-label filtering to only receive events that match all the specified labels.
 
-**Payments Transfers Events** - Transfer lifecycle notifications:
-- `payments.transfers.quoted` - Transfer created and awaiting execution
-- `payments.transfers.processing` - Transfer execution in progress
-- `payments.transfers.completed` - Transfer completed successfully
-- `payments.transfers.failed` - Transfer failed
-- `payments.transfers.travel_rule_incomplete` - Travel rule information is missing
-- `payments.transfers.travel_rule_completed` - Travel rule information has been provided and the transfer will proceed
-- **No labels required** - enable the transfers webhook to monitor status transitions
+Allows labels are:
+- `network` (required) — Blockchain network
+- `contract_address` — Smart contract address
+- `event_name` — Event name (e.g., "Transfer", "Burn")
+- `event_signature` — Event signature (e.g., "Transfer(address,address,uint256)")
+- `transaction_from` — Transaction sender address
+- `transaction_to` — Transaction recipient address
+- `params.*` — Any event parameter from the log event (e.g., `params.from`, `params.to`, `params.sender`, `params.tokenId`)
 
-**Wallet Events** - Wallet activity notifications:
-- `wallet.activity.detected`
+For webhook types that aren't `onchain.*`, labels are ignored.
 
 ### Webhook Signature Verification
-All webhooks include cryptographic signatures for security.
-The signature secret is returned in `secret` field when creating a subscription.
 
-**Note:** Webhooks are in beta and this interface is subject to change.
-
-See the [verification guide](https://docs.cdp.coinbase.com/onramp-&-offramp/webhooks#webhook-signature-verification) for implementation details.
+All webhooks include an HMAC-SHA256 signed header for security. The signature is signed with the secret that is returned in the `secret` field when creating a subscription.
 
-### Onchain Label Filtering
+Do not lose the secret, as you will not be able to recreate it. If you lose the secret, you will need to create a new subscription.
 
-For `onchain.activity.detected` events, use `labels` for precise filtering with AND logic (max 20 labels per webhook).
-
-**Allowed labels** (all in snake_case format):
-- `network` (required) - Blockchain network
-- `contract_address` - Smart contract address
-- `event_name` - Event name (e.g., "Transfer", "Burn")
-- `event_signature` - Event signature hash
-- `transaction_from` - Transaction sender address
-- `transaction_to` - Transaction recipient address
-- `params.*` - Any event parameter (e.g., `params.from`, `params.to`, `params.sender`, `params.tokenId`)
-
-**Examples**:
-- **Liquidity Pool Monitor**: `{"network": "base-mainnet", "contract_address": "0xcd1f9777571493aeacb7eae45cd30a226d3e612d", "event_name": "Burn"}`
-- **Price Oracle Tracker**: `{"network": "base-mainnet", "contract_address": "0xbac4a9428ea707c51f171ed9890c3c2fa810305d", "event_name": "PriceUpdated"}`
-- **DeFi Protocol Activity**: `{"network": "base-mainnet", "contract_address": "0x45c6e6a47a711b14d8357d5243f46704904578e3", "event_name": "Deposit"}`
+See the [verification guide](https://docs.cdp.coinbase.com/onramp-&-offramp/webhooks#webhook-signature-verification) for implementation details.
 
  * @summary Create webhook subscription
  */

package/src/openapi-client/generated/x402-facilitator/x402-facilitator.ts

@@ -18,6 +18,8 @@ import type {
   X402SearchResourcesResponse,
   X402SettleResponseResponse,
   X402SupportedPaymentKindsResponseResponse,
+  X402ValidateRequest,
+  X402ValidateResponse,
   X402VerifyResponseResponse,
 } from "../coinbaseDeveloperPlatformAPIs.schemas.js";
 
@@ -91,6 +93,7 @@ export const listX402DiscoveryResources = (
 /**
  * Gets x402 merchant discovery information for a given merchant payment address.
 This endpoint returns all active x402 resources associated with the specified `payTo` address, allowing clients to discover what payment-gated resources a merchant exposes and their corresponding payment requirements.
+If no active resources are found for the `payTo` address, the endpoint returns an empty `resources` list.
 The response is paginated, and by default, returns 20 items per page.
  * @summary List merchant discovery info
  */
@@ -137,6 +140,26 @@ export const postX402DiscoveryMcp = (
     options,
   );
 };
+/**
+ * Validates an x402 endpoint's bazaar-discovery configuration by probing the seller's URL live.
+Returns a uniform array of preflight check results (reachable, returns402, hasBazaarExtension, parse) and a simulated facilitator accept/reject decision so sellers and agents can confirm their endpoint is ready to be discovered before going live.
+This operation is read-only: it performs no payment and does not index the resource.
+ * @summary Validate x402 endpoint
+ */
+export const validateX402Resource = (
+  x402ValidateRequest: X402ValidateRequest,
+  options?: SecondParameter<typeof cdpApiClient<X402ValidateResponse>>,
+) => {
+  return cdpApiClient<X402ValidateResponse>(
+    {
+      url: `/v2/x402/validate`,
+      method: "POST",
+      headers: { "Content-Type": "application/json" },
+      data: x402ValidateRequest,
+    },
+    options,
+  );
+};
 export type VerifyX402PaymentResult = NonNullable<Awaited<ReturnType<typeof verifyX402Payment>>>;
 export type SettleX402PaymentResult = NonNullable<Awaited<ReturnType<typeof settleX402Payment>>>;
 export type SupportedX402PaymentKindsResult = NonNullable<
@@ -154,3 +177,6 @@ export type SearchX402ResourcesResult = NonNullable<
 export type PostX402DiscoveryMcpResult = NonNullable<
   Awaited<ReturnType<typeof postX402DiscoveryMcp>>
 >;
+export type ValidateX402ResourceResult = NonNullable<
+  Awaited<ReturnType<typeof validateX402Resource>>
+>;

package/src/version.ts

@@ -1 +1 @@
-export const version = "1.51.1";
+export const version = "1.51.2";