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.
Overview
Getting Started
Guides
Migration
Support
Changelog
Getting Started
Create a partner account, receive your access tier, and start with token discovery, quote checks, and swap creation.
Every partner API request uses a live API key in either the Authorization bearer header or the x-api-key header. API keys are shown in the partner portal and management dashboard, but they are never displayed inside these docs.
Authorization Header
Authorization: Bearer <your-api-key>Start by loading supported tokens, then quote the route, then create the swap, and finally poll the order status endpoint using the SWYPE Swap ID returned by the create response.
On This Page