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

The payment API from Pomo — 21 operation(s) for payment.

Pomo Payment API is one of 100 APIs that Pomo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payment. 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 21 operations across 21 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.

21 operations 21 paths 13 schemas 9 GET12 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 Payment API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (HTTPBearer).

Paths & Operations 21

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

payment 21
POST
/api/payment/subscription/resume
Resume Subscription
resume_subscription_api_payment_subscription_resume_post 1 param → 200422
POST
/api/payment/subscription/end-trial
End Trial And Start Paid Billing
end_trial_and_start_paid_billing_api_payment_subscription_end_trial_post 1 param → 200422
GET
/api/payment/subscription/{subscription_id}/payment-status
Get Subscription Payment Status
get_subscription_payment_status_api_payment_subscription__subscription_id__payment_status_get 1 param → 200422
GET
/api/payment/subscription/debug
Subscription Debug
subscription_debug_api_payment_subscription_debug_get → 200
GET
/api/payment/subscription/client-config
Subscription Client Config
subscription_client_config_api_payment_subscription_client_config_get → 200
GET
/api/payment/subscription/plans
Get Subscription Plans
get_subscription_plans_api_payment_subscription_plans_get → 200
POST
/api/payment/subscription/init-payment-element
Init Payment Element
init_payment_element_api_payment_subscription_init_payment_element_post body → 200422
POST
/api/payment/subscription/subscribe
Create Subscription
create_subscription_api_payment_subscription_subscribe_post body → 200422
POST
/api/payment/subscription/init-setup
Init Setup Intent
init_setup_intent_api_payment_subscription_init_setup_post body → 200422
POST
/api/payment/subscription/apply-coupon
Apply Coupon
apply_coupon_api_payment_subscription_apply_coupon_post body → 200422
POST
/api/payment/subscription/create-subscription
Create Subscription From Setup
create_subscription_from_setup_api_payment_subscription_create_subscription_post body → 200422
GET
/api/payment/subscription/current
Get Current Subscription
get_current_subscription_api_payment_subscription_current_get 1 param → 200422
POST
/api/payment/subscription/cancel
Cancel Subscription
cancel_subscription_api_payment_subscription_cancel_post 1 param body → 200422
POST
/api/payment/subscription/validate-plan-change
Validate Plan Change
validate_plan_change_api_payment_subscription_validate_plan_change_post body → 200422
POST
/api/payment/subscription/change-plan
Change Subscription Plan
change_subscription_plan_api_payment_subscription_change_plan_post body → 200422
GET
/api/payment/subscription/portal-session
Create Billing Portal Session
create_billing_portal_session_api_payment_subscription_portal_session_get 2 params → 200422
GET
/api/payment/subscription/payment-history
Get Payment History
get_payment_history_api_payment_subscription_payment_history_get 3 params → 200422
POST
/api/payment/subscription/checkout-session
Create Checkout Session
create_checkout_session_api_payment_subscription_checkout_session_post body → 200422
GET
/api/payment/subscription/checkout-session/{session_id}/status
Get Checkout Session Status
get_checkout_session_status_api_payment_subscription_checkout_session__session_id__status_get 1 param → 200422
GET
/api/payment/subscription/subscription-status
Get Subscription Status
get_subscription_status_api_payment_subscription_subscription_status_get 2 params → 200422
POST
/api/payment/subscription/webhook
Handle Stripe Webhook
handle_stripe_webhook_api_payment_subscription_webhook_post 1 param → 200422

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are PlanChangeValidationResponse (13 properties), PaymentHistoryItemResponse (10 properties), SubscriptionResponse (8 properties), SubscriptionTier (7 properties). Each schema is shown below with its type and property counts.

HTTPValidationError
object
1 property
PlanChangeValidationResponse
object
Response model for plan change validation.
13 properties 5 required
PaymentHistoryListResponse
object
Response model for payment history.
2 properties 2 required
SubscriptionResponse
object
Response model for subscription information.
8 properties 5 required
PaymentHistoryItemResponse
object
Response model for a payment history entry.
10 properties 4 required
CreateSubscriptionRequest
object
Request model for creating a subscription.
3 properties 1 required
ValidationError
object
3 properties 3 required
SubscriptionTier
object
Model representing a subscription tier.
7 properties 6 required
BillingPortalSessionResponse
object
Response model for a Stripe billing portal session.
2 properties 2 required
CancellationReason
string
High-level reason a user selects when cancelling a subscription. Kept in sync with the frontend cancellation reason form. The order here is not significant; va…
ValidatePlanChangeRequest
object
Request model for validating a plan change.
3 properties 2 required
ChangePlanRequest
object
Request model for changing subscription plan.
3 properties 2 required
CancelSubscriptionRequest
object
Request model for cancelling a subscription.
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pomo-payment-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 Payment 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.