SWYPE uses cookies and similar storage to keep the site secure, remember essential session state, and make payment flows work reliably.
Used for secure sign-in, payment-request continuity, fraud prevention, and account protection.
The current SWYPE experience does not rely on advertising cookies to operate the product shell.
Read the full notice on the cookie page. SWYPE never asks for wallet connect, private keys, or recovery phrases.
Developer Hub
Public swap API, private swap access, widgets, embeds, rate limits, migration notes, and support docs for partner integrations.
Getting Started
Guides
Support
Migration
Changelog
API Reference
Creates a protected SWYPE private swap using the live multi-provider private route engine.
POST
/api/partner/v1/swaps
Private swap creation requires a paid private or paid all-in-one access tier. The private route follows the current SWYPE private planner, so if the planner changes, partner private routing changes with it automatically.
Poll the order status endpoint with the SWYPE Swap ID to follow route progression. Private responses expose a SWYPE tracker state and protected status semantics without requiring SWYPE to publish the full private route decomposition publicly.
For protected routes, SWYPE should expose inspectable route semantics without exposing confidential planner internals. That means public documentation can describe the route as protected, multi-step, or confidentiality-oriented while still keeping exact planner rules private.
