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

Baserow Auth API

The Auth API from Baserow — 11 operation(s) for auth.

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

This API exposes 1 JSON Schema definition.

Tagged areas include Authentication. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and 1 JSON Schema.

This API exposes 15 operations across 11 paths, and defines 16 schemas. It is described by OpenAPI 3.0.3, at version 2.2.2.

Requests are made against the base URL https://api.baserow.io.

15 operations 11 paths 16 schemas 1 DELETE8 GET1 PATCH5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
2.2.2
Base URL
https://api.baserow.io
Authentication
HTTP Bearer, HTTP Bearer, HTTP Bearer
License
Resource Areas
1

Authentication & Security 3

Baserow Auth API declares 3 security schemes for authenticating requests. It accepts HTTP bearer tokens (Token your_token) (Database token). It accepts HTTP bearer tokens (JWT your_token) (JWT). It accepts HTTP bearer tokens (JWT your_token) (UserSource JWT).

Paths & Operations 15

Across 11 paths, the API surfaces 15 operations — 1 DELETE, 8 GET, 1 PATCH, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Auth 15
GET
/api/admin/auth-provider/
List all the available authentication providers.
list_auth_providers → 200
POST
/api/admin/auth-provider/
Creates a new authentication provider. This can be used to enable authentication with a third party service like Google or Facebook.
create_auth_provider → 200400
GET
/api/admin/auth-provider/{auth_provider_id}/
Get an authentication provider.
get_auth_provider 1 param → 200404
PATCH
/api/admin/auth-provider/{auth_provider_id}/
Updates a new authentication provider. This can be used to enable authentication with a third party service like Google or Facebook.
update_auth_provider 1 param → 200400404
DELETE
/api/admin/auth-provider/{auth_provider_id}/
Delete an authentication provider.
delete_auth_provider 1 param → 204404
GET
/api/auth-provider/login-options/
Lists the available login options for the configured authentication providers.
list_auth_providers_login_options → 200
GET
/api/sso/oauth2/callback/{provider_id}/
Processes callback from OAuth2 provider and logs the user in if successful.
oauth_provider_login_callback 2 params → 302
GET
/api/sso/oauth2/login/{provider_id}/
Redirects to the OAuth2 provider's authentication URL based on the provided auth provider's id.
oauth_provider_login_redirect 3 params → 302
POST
/api/sso/saml/acs/
Complete the SAML authentication flow by validating the SAML response. Sign in the user if already exists in Baserow or create a new one otherwise. Once authenticated, the user will be redirected to…
auth_provider_saml_acs_url body → 302
GET
/api/sso/saml/login/
This is the endpoint that is called when the user wants to initiate a SSO SAML login from Baserow (the service provider). The user will be redirected to the SAML identity provider (IdP) where the use…
auth_provider_saml_sp_login 4 params → 302
GET
/api/sso/saml/login-url/
Return the correct redirecturl to initiate the SSO SAML login. It needs an email address if multiple SAML providers are configured otherwise the only configured SAML provider signup URL will be retur…
auth_provider_login_url 4 params → 200400
GET
/api/two-factor-auth/configuration/
Returns two-factor auth configuration for the authenticated user.
two_factor_auth_configuration → 200
POST
/api/two-factor-auth/configuration/
Configures two-factor authentication for the authenticated user.
configure_two_factor_auth body → 200400401404
POST
/api/two-factor-auth/disable/
Disables two-factor authentication for the authenticated user.
disable_two_factor_auth body → 204403400
POST
/api/two-factor-auth/verify/
Verifies TOTP two-factor authentication
verify_totp_auth body → 200400401404429

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are OpenIdConnectAuthProviderModelAuthProvider (12 properties), SamlAuthProviderModelAuthProvider (9 properties), GitLabAuthProviderModelAuthProvider (8 properties), GitHubAuthProviderModelAuthProvider (7 properties). Each schema is shown below with its type and property counts.

PasswordAuthProviderModelAuthProvider
object
4 properties 2 required
Two_Factor_Auth_TypeCreateTwoFactorAuth
GitHubAuthProviderModelAuthProvider
object
7 properties 6 required
VerifyTOTP
object
3 properties 1 required
TOTPAuthProviderModelCreateTwoFactorAuth
object
4 properties 4 required
TOTPAuthProviderModelTwoFactorAuth
object
5 properties 5 required
SamlAuthProviderModelAuthProvider
object
9 properties 5 required
GitLabAuthProviderModelAuthProvider
object
8 properties 7 required
Authentication_ProviderAuthProvider
FacebookAuthProviderModelAuthProvider
object
7 properties 6 required
GoogleAuthProviderModelAuthProvider
object
7 properties 6 required
OpenIdConnectAuthProviderModelAuthProvider
object
12 properties 7 required
SAMLResponse
object
2 properties 2 required
DisableTwoFactorAuth
object
1 property 1 required
TOTPAuthProviderModelCreateTwoFactorAuthTypeEnum
string
totp - totp
Two_Factor_Auth_TypeTwoFactorAuth

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

baserow-auth-api-openapi.yml Raw ↑

Other APIs Baserow publishes across the network.

Baserow Admin API
Baserow Admin data scanner API
Baserow AI Assistant API
Baserow Applications API
Baserow Audit log API
Baserow Automation history API
Baserow Automation nodes API
Baserow Automation workflows API
Baserow Builder data sources API
Baserow Builder domains API
Baserow Builder elements API
Baserow Builder pages API
Where this information came from

This is an independent, third-party profile of Baserow 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.