restosignals-com Auth API
The Auth API from restosignals-com — 7 operation(s) for auth.
The Auth API from restosignals-com — 7 operation(s) for auth.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/restosignals-com:restosignals-com-auth-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: RestoSignals — restaurant opening-leads Auth API
description: Find restaurants & bars 1–6 months before they open. Fused liquor, permit and new-business signals, scored by opening_score.
version: 0.1.0
tags:
- name: Auth
paths:
/auth/signup:
post:
summary: Signup
operationId: signup_auth_signup_post
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
tags:
- Auth
/auth/confirm:
get:
summary: Auth Confirm
description: 'Mark the email verified from the link, then bounce to the dashboard. Key + credits are
already provisioned at signup, so this is verification only; welcome mail fires here.'
operationId: auth_confirm_auth_confirm_get
parameters:
- name: token
in: query
required: false
schema:
type: string
default: ''
title: Token
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
tags:
- Auth
/auth/confirm/resend:
post:
summary: Confirm Resend
operationId: confirm_resend_auth_confirm_resend_post
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
tags:
- Auth
/auth/login:
post:
summary: Login
operationId: login_auth_login_post
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
tags:
- Auth
/auth/forgot:
post:
summary: Forgot Password
description: 'Email a one-hour, single-use reset link. Same response whether or not the account exists,
so the form can''t be used to find out who has an account.'
operationId: forgot_password_auth_forgot_post
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
tags:
- Auth
/auth/reset:
post:
summary: Reset Password
operationId: reset_password_auth_reset_post
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
tags:
- Auth
/auth/logout:
post:
summary: Logout
operationId: logout_auth_logout_post
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
tags:
- Auth
components:
schemas:
ValidationError:
properties:
loc:
items:
anyOf:
- type: string
- type: integer
type: array
title: Location
msg:
type: string
title: Message
type:
type: string
title: Error Type
input:
title: Input
ctx:
type: object
title: Context
type: object
required:
- loc
- msg
- type
title: ValidationError
HTTPValidationError:
properties:
detail:
items:
$ref: '#/components/schemas/ValidationError'
type: array
title: Detail
type: object
title: HTTPValidationError