Skip to main content
After completing this workflow, you can send an authenticated request to the Sift REST or gRPC API.

​
Before you begin

​
How authentication works

Sift authenticates API requests using the Bearer scheme. For REST requests, the API key goes in the HTTP authorization header. For gRPC requests, the API key goes in an authorization header, passed as a metadata field, using the same Bearer scheme. The base URL routes the request to your environment. Use the API key and base URL from the same environment. See Use API keys across multiple environments if you connect to more than one.

​
Send an authenticated request

Replace $SIFT_API_KEY and $SIFT_REST_BASE_URL with your actual values, then run:

​
Verify your credentials work

A successful REST request returns HTTP status 200. A successful gRPC request returns a PingResponse.

​
Next steps

Ready to build a real integration? See Connect with an official client to use an official Python, Rust, or Go client.