Developer Tools › Guides
SDKs, Postman, and a signature debugger provide ready-made tools for the most time-consuming integration tasks.
Developer Tools
| Tool | Purpose |
|---|---|
| Signature debugger | Investigate 401 responses by comparing signing strings character by character |
| Postman collection | Try the flow before writing code |
| SDKs | Node / Python clients with signing and retry handling |
Start with the Signature Debugger
Around 90% of integration-stage 401 responses come from an incorrectly constructed signing string. Common causes are:
- PATH omitted from the signing string (most common)
- A timestamp in milliseconds
- Reserializing the body, changing indentation or key order
- Signing with
api_keyinstead ofsigning_key
The debugger breaks your input into components and compares the calculation. Everything runs in your browser; your key is never sent to us.
Postman
The collection is organized as product → group → endpoint, matching this site's structure. After importing it, set three environment variables (base_url / token / member_id) and run it.
The pre-request script calculates signatures and doubles as a readable signing reference implementation.