How to Get a Token on the S3zipper API

The S3zipper API authenticates requests with a bearer token. Tokens are short-lived, per-user, and replace the need to send your key and secret with every request.

Where to find your credentials

After signing in, open API Credentials and generate a key. You get two values:

• UserKey — identifies the account.
• UserSecret — proves the request comes from you. It is shown only once, so store it safely. If you lose it, generate a new credential.

Exchange the credentials for a token

curl -X POST https://api.s3zipper.com/gentoken \
  -d "userKey=YOUR_USERKEY" \
  -d "userSecret=YOUR_USERSECRET"

A successful response looks like this:

{"token":"eyJhbGciOiJIUzI1NiIs..."}

Use the token

Send it in the Authorization header as a bearer token on all API calls:

curl -H "Authorization: Bearer YOUR_TOKEN" \
  https://api.s3zipper.com/v1/jobs

What can go wrong

• 401 invalid credentials — the key or secret is wrong. Regenerate the credential if needed.
• Expired token — tokens expire after a day; request a fresh one with the same credentials.
• Missing or malformed token — check that the header is exactly Authorization: Bearer <token>.

Next: start your first zip job.