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 User API

The User API from Baserow — 17 operation(s) for user.

Baserow User 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 User. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and 1 JSON Schema.

This API exposes 17 operations across 17 paths, and defines 20 schemas. It is described by OpenAPI 3.2.0, at version 2.2.2.

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

17 operations 17 paths 20 schemas 1 GET3 PATCH13 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
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 User 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 17

Across 17 paths, the API surfaces 17 operations — 1 GET, 3 PATCH, 13 POST. Each is listed below with its method, path, parameters, and response codes.

User 17
POST
/api/user/
Create user
create_user body → 200400404
PATCH
/api/user/account/
Update account
update_account body → 200400
POST
/api/user/change-email/
Change email
change_email body → 204400
POST
/api/user/change-password/
Change password
change_password body → 204400
GET
/api/user/dashboard/
Dashboard
dashboard → 200
PATCH
/api/user/redo/
Redo
redo 1 param body → 200
POST
/api/user/reset-password/
Reset password
reset_password body → 204400
POST
/api/user/schedule-account-deletion/
Schedule account deletion
schedule_account_deletion → 204400
POST
/api/user/send-change-email-confirmation/
Send change email confirmation
send_change_email_confirmation body → 204400
POST
/api/user/send-reset-password-email/
Send password reset email
send_password_reset_email body → 204400
POST
/api/user/send-verify-email/
Send verify email
send_verify_email → 204
POST
/api/user/token-auth/
Token auth
token_auth body → 200401
POST
/api/user/token-blacklist/
Token blacklist
token_blacklist body → 204401
POST
/api/user/token-refresh/
Token refresh
token_refresh body → 200401
POST
/api/user/token-verify/
Token verify
token_verify body → 200401
PATCH
/api/user/undo/
Undo
undo 1 param body → 200
POST
/api/user/verify-email/
Verify email
verify_email body → 200400401

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are Register (8 properties), ActionScopes (7 properties), UserWorkspaceInvitation (6 properties), Account (5 properties). Each schema is shown below with its type and property counts.

ChangeEmail
object
1 property 1 required
PatchedUndoRedoRequest
object
1 property
ActionScopes
object
Mixin to a DRF serializer class to raise an exception if data with unknown fields is provided to the serializer.
7 properties
ResetPasswordBodyValidation
object
2 properties 2 required
EmailNotificationFrequencyEnum
string
instant - instant daily - daily weekly - weekly never - never
SendResetPasswordEmailBodyValidation
object
2 properties 2 required
ChangePasswordBodyValidation
object
2 properties 2 required
UserWorkspaceInvitation
object
This serializer is used for displaying the invitation to the user that doesn't have access to the workspace yet, so not for invitation management purposes.
6 properties 6 required
TokenBlacklist
object
1 property 1 required
TokenRefreshWithUser
object
3 properties 1 required
UndoRedoAction
object
2 properties
Dashboard
object
1 property 1 required
SendChangeEmailConfirmation
object
3 properties 3 required
TokenObtainPairWithUser
object
3 properties 1 required
TokenVerifyWithUser
object
2 properties 1 required
UndoRedoResponse
object
2 properties 2 required
Account
object
This serializer must be kept in sync with UserSerializer.
5 properties
PatchedAccount
object
This serializer must be kept in sync with UserSerializer.
5 properties
Register
object
8 properties 3 required
VerifyEmailAddress
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

baserow-user-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 Auth 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
Where this information came from

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