Registration & Authentication
Create an Account
You can sign up at app.pickpad.ai, or register through the API if you're integrating directly.
POST /account/register
{
"email": "merchant@example.com",
"password": "your-password"
}
Response:
{
"success": true,
"access_token": "eyJhbGciOiJIUzI1NiIs..."
}
The access_token you get back is a JWT — hang onto it, since you'll need it for every authenticated request.
The email you register with becomes the account's first Administrator. You can invite more people later with their own logins and roles — see Users & Roles.
Login
Every team member logs in with their own email and password. Emails aren't case-sensitive, and deactivated users can't log in.
POST /account/login
{
"email": "merchant@example.com",
"password": "your-password"
}
Response:
{
"success": true,
"access_token": "eyJhbGciOiJIUzI1NiIs..."
}
Authentication
Every authenticated endpoint expects a Bearer token in the Authorization header:
Authorization: Bearer <access_token>
The token carries the signed-in user, so each request gets that user's role and rights. If the
role doesn't allow an action, the API answers 403 Forbidden.
API Keys
Webhook integrations work a little differently — instead of a JWT, you authenticate with an API key.
Creating an API Key
- Log in to the Pickpad Dashboard as an Administrator or Integrator
- Go to Settings and select Webhooks as your order source
- An API keys section will appear — click Create API Key
- Copy the key and store it somewhere safe
Using an API Key
Pass the API key in the x-api-key header:
x-api-key: <your-api-key>
API keys only work with the POST /distribution/webhook/generic endpoint — they won't authenticate anything else.