# BLIPS Developers ## Docs - [Create a customer-bound external account for your authenticated platform.](https://docs.blips.network/api-reference/accounts/create-a-customer-bound-external-account-for-your-authenticated-platform.md): Create a customer-bound external account for your authenticated platform. `platformAccountId` is the platform-side mapping field, while `accountInfo` is the bounded external-account details block. The response returns only safe masked account details. - [Delete customer external account](https://docs.blips.network/api-reference/accounts/delete-customer-external-account.md): Delete one customer-bound external account for your authenticated platform on the canonical `/customers/external-accounts` public path family. - [List customer-bound external accounts for your authenticated platform.](https://docs.blips.network/api-reference/accounts/list-customer-bound-external-accounts-for-your-authenticated-platform.md): List customer-bound external accounts for your authenticated platform with optional customer and currency filters plus cursor pagination. This is a safe masked ExternalAccount readback surface rather than platform-owned account management or Customer CRUD. - [List customer-owned internal accounts.](https://docs.blips.network/api-reference/accounts/list-customer-owned-internal-accounts.md): Read customer-owned internal accounts with optional currency, customerId, and cursor filters. This surface is distinct from GET /platform/internal-accounts. In the current MVP, same-currency funding is performed separately via POST /transfer-in. - [Create lookup-backed PPV quote.](https://docs.blips.network/api-reference/cross-currency-transfers/create-lookup-backed-ppv-quote.md): Create a lookup-backed PPV quote from a funded internal account to a receiver PPV address. Use GET /quotes/{quoteId}/current for live/current quote state, GET /quotes/{quoteId} for retained historical detail, and POST /quotes/{quoteId}/execute for execution. This endpoint creates the quote only and… - [Execute a previously created quote.](https://docs.blips.network/api-reference/cross-currency-transfers/execute-a-previously-created-quote.md): Execute a quote that was created earlier through POST /quotes after any optional readback through GET /quotes/{quoteId}/current or GET /quotes/{quoteId}. The public execute contract is body-less, can include an optional `Idempotency-Key`, and returns the bounded execution acceptance result linked by… - [Get quote detail by ID.](https://docs.blips.network/api-reference/cross-currency-transfers/get-quote-detail-by-id.md): Read the retained historical detail for a quote. This is the secondary historical-detail route; GET /quotes/{quoteId}/current remains the default live/current quote readback path. - [List quote inventory/history summary rows](https://docs.blips.network/api-reference/cross-currency-transfers/list-quote-inventoryhistory-summary-rows.md): Browse retained quote inventory/history summary rows. This operation is part of the current public API walkthrough. - [Read the default live/current state of a quote.](https://docs.blips.network/api-reference/cross-currency-transfers/read-the-default-livecurrent-state-of-a-quote.md): Read the default live/current quote-state view for a quote created earlier through POST /quotes. This is the primary current-state readback path; use GET /quotes/{quoteId} for retained historical detail. - [Resolve receiver by PPV address](https://docs.blips.network/api-reference/cross-currency-transfers/resolve-receiver-by-ppv-address.md): Resolve a receiver by public PPV address in the PPV-first flow before quote creation. Returns the lookupId required by POST /quotes. - [Create a customer for your authenticated platform.](https://docs.blips.network/api-reference/customers/create-a-customer-for-your-authenticated-platform.md): Create a customer record for your authenticated platform. This public customer-create contract creates the customer only; PPV/payment-address issuance remains a later explicit action. - [Delete customer by ID](https://docs.blips.network/api-reference/customers/delete-customer-by-id.md): Delete one customer record for your authenticated platform. Deleting a customer also removes or invalidates customer-bound resources, and repeated delete returns 410. - [Get customer detail](https://docs.blips.network/api-reference/customers/get-customer-detail.md): Read one customer detail record for your authenticated platform. `ppvAddress` is current-state readback only and remains null until a customer payment address is explicitly issued. - [Issue the customer's singleton PPV payment address.](https://docs.blips.network/api-reference/customers/issue-the-customers-singleton-ppv-payment-address.md): Issue or return the customer's singleton PPV payment address for your authenticated platform. This customer-scoped action has no request body, issues under the configured `ppvDomain`, and returns the existing active address idempotently instead of creating a second one. - [List customers](https://docs.blips.network/api-reference/customers/list-customers.md): List customers for the current platform scope. This operation is part of the current public API walkthrough. - [Update customer](https://docs.blips.network/api-reference/customers/update-customer.md): Update mutable customer-record fields for your authenticated platform. External-account changes stay on `/customers/external-accounts` and PPV/payment-address issuance stays on `/customers/{customerId}/payment-address`. - [Get your current platform configuration](https://docs.blips.network/api-reference/platform-setup/get-your-current-platform-configuration.md): Read your current platform configuration. Basic Auth binds this request to your platform. Platform identity remains outside this public config contract. - [Update your current platform configuration](https://docs.blips.network/api-reference/platform-setup/update-your-current-platform-configuration.md): Update and save your current platform configuration. Basic Auth binds this request to your platform. Platform identity fields remain locked after create. - [Create same-currency incoming funding transfer](https://docs.blips.network/api-reference/same-currency-transfers/create-same-currency-incoming-funding-transfer.md): Create a same-currency incoming funding transfer from a bound external account into a customer internal account. - [Create same-currency outgoing payout or withdrawal](https://docs.blips.network/api-reference/same-currency-transfers/create-same-currency-outgoing-payout-or-withdrawal.md): Create a same-currency outgoing payout or withdrawal from a customer internal account to a bound external account. - [Resolve same-currency receiver readiness by external account ID.](https://docs.blips.network/api-reference/same-currency-transfers/resolve-same-currency-receiver-readiness-by-external-account-id.md): Resolve same-currency receiver readiness by external account ID. Use this before same-currency payout, incoming funding, or related follow-on steps. - [Get sandbox Lightning execution profile](https://docs.blips.network/api-reference/sandbox-api/get-sandbox-lightning-execution-profile.md): Read the platform-scoped Sandbox Lightning Network Execution Profile singleton. If the platform has not saved an explicit profile yet, BLIPS returns the default singleton values. This sandbox resource is a quote-input surface only and affects newly created quotes after corridor confirmation, does no… - [Simulate incoming payment review case](https://docs.blips.network/api-reference/sandbox-api/simulate-incoming-payment-review-case.md): Create one synthetic incoming-payment review case for sandbox, public-test, and Playground use. The created case feeds the existing transaction review flow: inspect it via GET /transactions or GET /transactions/{transactionId}, reject it via POST /transactions/{transactionId}/reject, and, when allow… - [Update sandbox Lightning execution profile](https://docs.blips.network/api-reference/sandbox-api/update-sandbox-lightning-execution-profile.md): Partially update the platform-scoped Sandbox Lightning Network Execution Profile singleton. Only btcFiatSpreadBps and lockPriceDurationSeconds are writable. Updated values affect newly created quotes after corridor confirmation; existing quotes keep their stored snapshot and POST /quotes remains the… - [Create an API token for your authenticated platform.](https://docs.blips.network/api-reference/tokens/create-an-api-token-for-your-authenticated-platform.md): Create one API token for your authenticated platform. The request body requires a `name` plus at least one permission from `view` or `manage`. The operator-issued root manage token remains visible but is not created here. `clientSecret` is returned once on create only. - [Get API token detail for your authenticated platform.](https://docs.blips.network/api-reference/tokens/get-api-token-detail-for-your-authenticated-platform.md): Retrieve one API token visible on your authenticated platform. The operator-issued root manage token remains visible as read-only context. This route accepts the public `Token:` form returned by list/create surfaces and the raw runtime token id. `clientSecret` is never returned on detail readbac… - [List API tokens for your authenticated platform.](https://docs.blips.network/api-reference/tokens/list-api-tokens-for-your-authenticated-platform.md): Retrieve the API tokens visible on your authenticated platform. The operator-issued root manage token appears as read-only context. Platform-created tokens can carry `view`, `manage`, or both permissions. `clientSecret` is never returned on list surfaces. - [Revoke an API token for your authenticated platform.](https://docs.blips.network/api-reference/tokens/revoke-an-api-token-for-your-authenticated-platform.md): Revoke one platform-created API token without deleting the token record. The operator-issued root manage token is visible in list/detail but returns `403 TOKEN_NOT_REVOCABLE` here. `clientSecret` is never returned on revoke responses. - [Approve incoming transaction.](https://docs.blips.network/api-reference/transactions/approve-incoming-transaction.md): Approve a pending incoming transaction after it enters receiver review. Provide `receiverCustomerInfo` only when the pending incoming transaction explicitly requested additional receiver fields during review. For the Step 4 sandbox scenarios, `sanctions_hit` and `sender_kyc_not_approved` are hard re… - [Get transaction by ID](https://docs.blips.network/api-reference/transactions/get-transaction-by-id.md): Read one direction-aware public transaction detail by transactionId. This canonical public detail route returns either the Outgoing Transaction or Incoming Transaction variant. For Step 4 incoming review cases, the incoming variant may additionally expose `reviewReason`, `decisionMode`, `recommended… - [Reject incoming transaction.](https://docs.blips.network/api-reference/transactions/reject-incoming-transaction.md): Reject a pending incoming transaction after it enters receiver review. Provide a receiver-side rejection reason in the request body using the current uppercase BLIPS reason-token format. - [Verify webhook connectivity](https://docs.blips.network/api-reference/webhooks/verify-webhook-connectivity.md): Verify that your configured public webhook endpoint is reachable during platform setup. This endpoint is a support verification helper, not the incoming-review business callback contract. - [Authentication](https://docs.blips.network/authentication.md): How BLIPS credentials map into the first public API contract and the Mintlify Playground. - [Demo Overview](https://docs.blips.network/demo/overview.md): How the BLIPS demo should be exposed as a website-owned surface without being merged into the docs runtime. - [Demo Scenarios](https://docs.blips.network/demo/scenarios.md): The runtime surfaces that should be preserved when the BLIPS demo is attached to its public domain. - [Errors](https://docs.blips.network/errors.md): The public BLIPS error shape and what should be documented outside the generated endpoint pages. - [BLIPS Developers](https://docs.blips.network/index.md): The public developer entrypoint for BLIPS API reference, Playground, authentication, and demo access. - [Quickstart](https://docs.blips.network/quickstart.md): The shortest path from BLIPS credentials to a first successful API request. - [API Reference Overview](https://docs.blips.network/reference/overview.md): How the BLIPS public API reference is organized inside Mintlify. - [Playground](https://docs.blips.network/reference/playground.md): How BLIPS Try It is bound to the Public Test Backend and what remains intentionally outside the public boundary. - [First-Release Checklist](https://docs.blips.network/reference/release-checklist.md): Final public checklist for the first BLIPS Mintlify reference and Public Test Backend Try It release. - [Sandbox APIs](https://docs.blips.network/reference/sandbox-apis.md): Public Test and demo-only sandbox surfaces that either feed quote creation or create Step 4 review cases without becoming second business API families. - [Webhooks](https://docs.blips.network/webhooks.md): The current webhook documentation boundary and how it should move into OpenAPI 3.1 over time. ## OpenAPI Specs - [blips-public-reference](https://docs.blips.network/openapi/blips-public-reference.yaml) - [openapi](https://docs.blips.network/api-reference/openapi.json)