GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Documentation
  • API Reference
  • Introduction to Socket API
  • Creating and Managing API Tokens
  • Authentication
  • Quota
  • Rate Limits
  • Socket Package URLs (purl)
  • Historical Data Endpoints
  • API Lifecycle and Deprecation Process
  • Packages
  • List published versions for a package by PURLget
  • Deprecated
  • Diff Full Scansget

This view

  • Original page
  • New address

GeezerVison is showing docs.socket.dev — Authentication

Socket's API uses organization tokens for authenticating requests.

Organization tokens can be created in your Socket organization settings and are scoped to the organization that you create them in.

Authenticating requests to the Socket API can be done by passing the API token as a Bearer token in the Authorization header, or as the username field of an HTTP Basic authentication header.

To authenticate using a Bearer token, pass the API token in the Authorization header after the word "Bearer":

curl --request GET \
     --url 'https://api.socket.dev/v0/orgs/org_slug/full-scans' \
     --header 'accept: application/json' \
     --header 'authorization: Bearer your_api_key'

To authenticate a request, provide your API token through HTTP Basic authentication in the request. The API token is used as the username and the password is left blank (ie. your_api_key: encoded in Base64).

An example is shown below:

curl https://api.socket.dev/v0/quota -X GET -u "your_api_key:"

Updated 5 months ago


Did this page help you?

Updated 5 months ago


Did this page help you?
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.