Login Endpoint

The login endpoint authenticates a vendor using their Triand account credentials and returns a Bearer token (PJWT) for subsequent API calls.

POST https://api.triand.com/v1/login

A successful login returns:

{
  "actionOk": true,
  "error": [],
  "pjwt": "eyJhbGciOiJIUzUxMiI...",
  "expiresIn": 86400
}

curl -X POST https://api.triand.com/v1/login \
  -H "Content-Type: application/json" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{
    "email": "vendor@example.com",
    "password": "your-password"
  }'

const response = await fetch('https://api.triand.com/v1/login', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'x-api-key': 'YOUR_API_KEY',
  },
  body: JSON.stringify({
    email: 'vendor@example.com',
    password: 'your-password',
  }),
})
const { pjwt, expiresIn } = await response.json()

// Use the pjwt for subsequent API calls:
const students = await fetch('https://api.triand.com/v1/students', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'x-api-key': 'YOUR_API_KEY',
    'Authorization': `Bearer $`,
  },
  body: JSON.stringify({ limit: 5, districtlea: '1503000' }),
})

The PJWT token expires after 24 hours (expiresIn: 86400 seconds). When the token expires, your API calls will return a 401 invalid-token error. At that point, call POST /v1/login again to obtain a fresh token.

Best practice: Cache the PJWT and re-authenticate proactively before it expires, rather than waiting for a 401 error. Track the expiresIn value to know when to refresh.