How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

SnapAPI Auth API

Authentication — register, login, OAuth, password reset, email verification

SnapAPI Auth API is one of 13 APIs that SnapAPI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Authentication. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 11 operations across 11 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://api.snapapi.pics.

11 operations 11 paths 3 schemas 2 GET9 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://api.snapapi.pics
Authentication
API Key, HTTP Bearer
Resource Areas
1

Authentication & Security 2

SnapAPI Auth API declares 2 security schemes for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyAuth). It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

  • ApiKeyAuth — Your SnapAPI API key
  • BearerAuth — JWT access token obtained from /auth/login or /auth/refresh

Paths & Operations 11

Across 11 paths, the API surfaces 11 operations — 2 GET, 9 POST. Each is listed below with its method, path, parameters, and response codes.

Auth 11

Authentication — register, login, OAuth, password reset, email verification

POST
/auth/register
Register
register body → 200400429
POST
/auth/login
Login
login body → 200401403429
POST
/auth/google
Google OAuth
googleAuth body → 200400501
POST
/auth/github
GitHub OAuth
githubAuth body → 200400501
POST
/auth/apple
Apple Sign-In
appleAuth body → 200400
POST
/auth/refresh
Refresh Token
refreshToken → 200401
POST
/auth/logout
Logout
logout → 200
GET
/auth/me
Get Current User
getCurrentUser → 200401
POST
/auth/forgot-password
Forgot Password
forgotPassword body → 200429
POST
/auth/reset-password
Reset Password
resetPassword body → 200400
GET
/auth/verify-email
Verify Email
verifyEmail 1 param → 302400

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are UserObject (8 properties), AuthResponse (4 properties), Error (3 properties). Each schema is shown below with its type and property counts.

UserObject
object
8 properties
Error
object
3 properties
AuthResponse
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

snapapi-pics-auth-api-openapi.yml Raw ↑

Other APIs SnapAPI publishes across the network.

SnapAPI Analyze API
SnapAPI Dashboard API
SnapAPI Extract API
SnapAPI Health API
SnapAPI PDF API
SnapAPI Scrape API
SnapAPI Screenshot API
SnapAPI Storage API
SnapAPI Usage API
SnapAPI Utilities API
SnapAPI Video API
SnapAPI Webhooks API
Where this information came from

This is an independent, third-party profile of SnapAPI Auth API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.