~/security

Security at API.SH

This page describes what we actually do to protect your account, your keys and your data today. It's written to be checked: if something here doesn't match what you see, tell us.

Data in transit

  • The website, the dashboard and the API are served over HTTPS (TLS), and webhooks we send go only to https:// addresses.
  • Dashboard sign-ins use cookies marked HttpOnly, Secure and SameSite=Lax, so page scripts can't read them and browsers don't send them with cross-site requests.

Keys, passwords and secrets

  • API keys are shown to you once, when you create them. We store only a SHA-256 hash and a short prefix so you can tell keys apart. If a key leaks, revoke it on the keys page and it stops working.
  • Passwords are stored as salted PBKDF2-SHA256 hashes, never in readable form. You can also sign in with a one-time email code or with Google, and avoid passwords entirely.
  • Two-factor login (any authenticator app) is available to every user, with single-use recovery codes. Teams can require it for every member.
  • Secrets we must be able to read back, such as two-factor seeds, single sign-on client secrets and webhook signing secrets, are encrypted with AES-GCM before they are stored. Provisioning tokens are stored only as hashes.

Access control for teams

  • Every team member has a role (owner, admin, developer, billing or viewer), and the server checks it on every request, not just the interface.
  • Keys belong to the team. Each key can have an expiry date, a monthly credit cap and a list of allowed endpoints.
  • Every change to a team (members, roles, keys, billing and settings) is written to an activity log that the team can see.
  • Teams with the enterprise features (included from $1,000 a month) can also use single sign-on (SAML 2.0 or OpenID Connect), SCIM provisioning, network allow-lists for keys and for the dashboard, a maximum session length, audit log export and signed audit webhooks. See the Enterprise guides.

Staff access to your account

Sometimes support needs to see what you see to fix a problem. When that happens:

  • Only senior staff can do it, and they must enter their own password and a two-factor code each time.
  • They have to give a reason, and that reason is shown to you.
  • A visit lasts at most 30 minutes and is view-only unless changes are needed to resolve your request.
  • Every visit is recorded and listed in your dashboard under settings → support access, with what was changed, if anything.

Your data

  • What we keep: your account details, your API usage and billing records, and a copy of each successful API response so you can download it again for free. You can download a response again for 30 days. We keep each account's most recent response copies by plan and an encrypted archive of older ones, which we use to enrich our database of public web data; you can opt out by asking us to delete your responses; Enterprise teams can instead choose 0, 1, 7, 31 or 90 days, and then copies are deleted at that age and never archived (0 means we keep none).
  • Payments are handled by our payment provider. We never see or store your full card number.
  • We don't sell data and don't use advertising trackers. The details are in our privacy policy.
  • Deleting your account is available under settings in the dashboard. It removes your personal data straight away; your usage logs are de-identified and then deleted after 180 days, and invoices are kept as tax law requires.

Abuse protection

  • Sign-up, sign-in, one-time codes and password resets are protected by an automated human check, and one-time codes stop working after a few wrong tries.
  • Calls refused by your own security settings (an expired key, a network allow-list, a credit cap, an endpoint the key isn't allowed to call) are never charged, and neither are calls held back by a team's rate limit.

Certifications and reviews

We don't hold SOC 2 or ISO 27001 certification today, and we won't claim otherwise. If your company needs a security review, Enterprise customers can send us their questionnaire and we'll answer it honestly, point by point.

Reporting a vulnerability

If you think you've found a security problem in API.SH, please email security@api.sh. Include what you found, how to reproduce it and what impact you think it has.

  • We'll confirm we've received it, keep you updated while we fix it, and credit you publicly if you'd like.
  • Please test only against your own account, don't access or change other people's data, don't run load or denial-of-service tests, and give us reasonable time to fix the issue before telling anyone else.
  • We won't take legal action against good-faith research that follows these guidelines.
  • We don't run a paid bug bounty program at the moment.

Questions about this page: support@api.sh.