Concepts
Flow actions
login, signup, link, sign, and confirm — when to use each action with required scopes.
Every user-facing pasby flow includes an action in the request body. The action controls UX copy (payload) and which scopes apply.
Identification actions
Used with identification endpoints.
| Action | Purpose | Typical scopes |
|---|---|---|
login | Authenticate a returning pasby user | identification:same, identification:another, identification:wildcard |
signup | Onboard a new identity | Same as login |
link | Link pasby identity to an existing account in your app | Same as login |
{
"action": "login",
"claims": ["naming.given", "contact.email"],
"payload": "Sign in to Acme"
}Signing actions
Used with signing endpoints.
| Action | Webhook required | Purpose |
|---|---|---|
sign | Yes | Cryptographic signature |
confirm | No | Transaction confirmation |
See Webhooks when action is sign.
Related
- Claims reference — data to request per action
- Choose your integration path