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

Pomo Auth API

The auth API from Pomo — 12 operation(s) for auth.

Pomo Auth API is one of 100 APIs that Pomo 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, an API reference, API documentation, authentication docs, and rate-limit docs.

This API exposes 12 operations across 12 paths, and defines 13 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against a single base URL, https://api.usepomo.ai.

12 operations 12 paths 13 schemas 5 GET7 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.usepomo.ai
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Pomo Auth API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (HTTPBearer).

Paths & Operations 12

Across 12 paths, the API surfaces 12 operations — 5 GET, 7 POST. Each is listed below with its method, path, parameters, and response codes.

auth 12
GET
/api/auth/status
Check Registration Status
check_registration_status_api_auth_status_get → 200
POST
/api/auth/registration/touch
Touch Registration Lead
touch_registration_lead_api_auth_registration_touch_post body → 200422
POST
/api/auth/register/init
Register Init
register_init_api_auth_register_init_post body → 200422
POST
/api/auth/register/finalize
Register Finalize
register_finalize_api_auth_register_finalize_post body → 200422
GET
/api/auth/invitation
Get Invitation Info From Query
get_invitation_info_from_query_api_auth_invitation_get 1 param → 200422
GET
/api/auth/invitation/{invite_token}
Get Invitation Info
get_invitation_info_api_auth_invitation__invite_token__get 1 param → 200422
POST
/api/auth/accept-invitation
Accept Invitation
accept_invitation_api_auth_accept_invitation_post body → 200422
POST
/api/auth/register
Register User
register_user_api_auth_register_post body → 200422
GET
/api/auth/me
Get User Profile
get_user_profile_api_auth_me_get → 200
POST
/api/auth/update-profile
Update User Profile
update_user_profile_api_auth_update_profile_post body → 200422
POST
/api/auth/logout
Logout
logout_api_auth_logout_post → 200
GET
/api/auth/health
Health Check
health_check_api_auth_health_get → 200

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are InvitationInfoResponse (12 properties), User (11 properties), RegistrationFormData (9 properties), UserUpdate (8 properties). Each schema is shown below with its type and property counts.

HTTPValidationError
object
1 property
AcceptInvitationRequest
object
Request schema for accepting an organization invitation. Used by both new users and existing users joining additional organizations.
5 properties 2 required
FinalizeRegistrationRequest
object
Finalize registration by marking status complete and recording selected plan.
2 properties
ValidationError
object
3 properties 3 required
InvitationProfileAccess
object
Profile access details attached to an invite.
3 properties 2 required
AcceptInvitationResponse
object
Response from accept invitation endpoint.
7 properties 2 required
RegistrationTouchResponse
object
Response after recording a registration funnel event.
4 properties 4 required
UserUpdate
object
Schema for user profile updates. Status changes require admin privileges.
8 properties
RegistrationResponse
object
Response from registration endpoint (new users creating their own organization).
7 properties 2 required
RegistrationTouchRequest
object
Record a pre-registration page or lifecycle event after Clerk auth.
4 properties 1 required
RegistrationFormData
object
Registration form data for NEW users creating their own organization. For accepting invitations, use AcceptInvitationRequest instead.
9 properties 5 required
InvitationInfoResponse
object
Response from invitation preview endpoint.
12 properties 5 required
User
object
11 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pomo-auth-api-openapi.yml Raw ↑

Other APIs Pomo publishes across the network.

Pomo Ab Groups API
Pomo Agent Jobs API
Pomo Agentic Chat API
Pomo Agentic Conversations API
Pomo Agentic Tasks API
Pomo Agentic Teams API
Pomo Agentic User API
Pomo AI Campaign API
Pomo AI Personas API
Pomo AI Policy API
Pomo AI Product Lab API
Pomo AI Testing API
Where this information came from

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