Create a Stripe checkout session

POST /api/stripe/create-checkout-session on the Vigilbase One API.

Needs a recent sign-in

POST/api/stripe/create-checkout-session

One accepts this request only with a recent sign-in; renewing a token doesn't count, and MCP sessions and API keys are always refused. See changes that need a recent sign-in.

Authorizations

AuthorizationstringAccess tokenheaderrequired

Bearer access token from Vigilbase Identity (auth.vigilbase.com), sent as Authorization: Bearer <token>. The CLI gets one with vigilbase login. Organisation API keys can't call this endpoint: it needs a recent sign-in by a person.

Permissions checkedwrite:billing

Body

application/json

lead_idstringuuid

product_keystring

operation_idstringuuidrequired

bandwidth_limitnumberrequired

domainstring

dns_recordsobject[]

8 child attributes

idstringrequired

namestringrequired

typestringrequired

One of:AAAAACNAMEMXTXTNSSRVCAA

contentstringrequired

ttlnumberrequired

minimum 60maximum 86400

prioritynumber

minimum 0maximum 65535

proxiedboolean

commentstring

customer_emailstringemail

customer_namestring

billing_addressobject

6 child attributes

line1stringrequired

line2string | nullrequired

citystringrequired

statestringrequired

postal_codestringrequired

countrystringrequired

has_agreed_to_liabilityboolean

include_onboardingboolean

success_urlstringuri

cancel_urlstringuri

first_namestring

last_namestring

phonestring

company_namestring

selected_tierinteger

minimum 1maximum 3

bandwidth_tbnumber

Response

Success

# Token from `vigilbase login`. API keys can't call this.
curl --request POST \
  --url 'https://one.vigilbase.com/api/stripe/create-checkout-session' \
  --header "Authorization: Bearer $VIGILBASE_TOKEN" \
  --header 'Content-Type: application/json' \
  --data '{"lead_id":"<uuid>","product_key":"<string>","operation_id":"<uuid>","bandwidth_limit":123,"domain":"<string>","dns_records":[{"id":"<string>","name":"<string>","type":"A","content":"<string>","ttl":123,"priority":123,"proxied":true,"comment":"<string>"}],"customer_email":"<string>","customer_name":"<string>","billing_address":{"line1":"<string>","line2":"<string>","city":"<string>","state":"<string>","postal_code":"<string>","country":"<string>"},"has_agreed_to_liability":true,"include_onboarding":true,"success_url":"<uri>","cancel_url":"<uri>","first_name":"<string>","last_name":"<string>","phone":"<string>","company_name":"<string>","selected_tier":123,"bandwidth_tb":123}'

Set VIGILBASE_TOKEN to an Identity access token first, or use Try it.

Responses

200Success

401Authentication required

403Not permitted

The catalog doesn't include example response bodies for this endpoint.

Was this page helpful?