Authentication

Every request to the pckt.sh API gateway is authenticated with a Bearer token in the Authorization header.

Getting your API key

  1. Sign up or log in to your pckt.sh account
  2. Open the API Keys section of your dashboard
  3. Create a new API key and copy it somewhere safe

Using your API key

Include your key as a Bearer token on every request:

Authorization: Bearer YOUR_API_KEY

Using gRPC

Endpoints on plans with gRPC access can also be called directly over gRPC at grpc.pckt.sh:443. There's no separate credential — send the same API key as an authorization metadata entry instead of an HTTP header:

authorization: bearer YOUR_API_KEY

The server has reflection enabled, so you can explore and call any endpoint with grpcurl without needing the .proto files:

grpcurl -H 'authorization: bearer YOUR_API_KEY' grpc.pckt.sh:443 list

Each endpoint's page lists its gRPC method path and a ready-to-run grpcurl command, where available.

Try it from these docs

Save your key below and it will be used automatically by the playground on every endpoint page.

Stored only in this browser's local storage — never sent to pckt.sh. Used to authenticate requests you send from the playground on these docs.

Need an API key?

Sign up for free and get 500 requests/month.

Get Started

Search API reference

Search endpoints by name, description, or parameter