Buy an add-on offer for the signed-in user
A one-time, lifetime or consumable offer opens a Stripe Checkout session on the person's own customer; a recurring offer is added to the person's own...
Warning
Not fully described yet. The API description has no described successful answer for this operation yet. The method, path, sign-in, rate limits and request fields on this page are read from the server's code and are accurate; what a successful call returns is not written down here yet. Until it is, search engines and the agent index leave this page out.
POST/api/v1/public/me/billing/checkout
- Sign-in
- A signed-in user's session: send the session id in the x-session-id header.
- Rate limit
- Up to 500 requests every 3 seconds per IP address; up to 1,000 requests a minute per API key (some requests are not counted); up to 30 requests a minute per IP address.
A one-time, lifetime or consumable offer opens a Stripe Checkout session on the person's own customer; a recurring offer is added to the person's own subscription with no session, answered added or payment_required. Refused with 409 STRIPE_NOT_CONNECTED when the app has no Stripe account, 409 IDEMPOTENCY_KEY_REUSED for an Idempotency-Key sent again with another purchase, and in the management tenant 403 EMAIL_NOT_VERIFIED for an unverified email.
Request
Send the body as application/json.
Body
| Field | Type | Required | Constraints | Description |
|---|---|---|---|---|
offerSlug | string | Yes | 1 to 100 characters | - |
quantity | integer | No | at least 1, at most 1000 | - |
currency | string | No | 3 to 3 characters | - |
promotionCode | string | No | 1 to 64 characters | - |
successUrl | string | No | format uri | - |
cancelUrl | string | No | format uri | - |
uiMode | string | No | one of "hosted", "embedded" | - |
returnUrl | string | No | format uri | - |
prorationDate | string | No | format date-time | - |
metadata | object | No | - | - |
Example request
Replace each YOUR_... value with your own, and set the credential in the environment variable the sample reads.
curl -X POST "https://api.console.buildbase.app/api/v1/public/me/billing/checkout" \
-H "x-session-id: $BUILDBASE_SESSION_ID" \
-H "Content-Type: application/json" \
-d '{
"offerSlug": "string"
}'const response = await fetch(
'https://api.console.buildbase.app/api/v1/public/me/billing/checkout',
{
method: 'POST',
headers: {
'x-session-id': process.env.BUILDBASE_SESSION_ID ?? '',
'Content-Type': 'application/json',
},
body: JSON.stringify({
offerSlug: 'string',
}),
}
);
if (!response.ok) {
throw new Error(`${response.status}: ${await response.text()}`);
}
const data = await response.text();import os
import requests
response = requests.post(
"https://api.console.buildbase.app/api/v1/public/me/billing/checkout",
headers={
"x-session-id": os.environ["BUILDBASE_SESSION_ID"],
},
json={
"offerSlug": "string",
},
timeout=30,
)
response.raise_for_status()
data = response.textResponses
A successful answer is not described yet. The server answers with the status and body its handler sends.
Any other status
The handler's own answer. Not described yet: response bodies come from captured responses (server/openapi/captured) and overlays (server/openapi/overlays).
Errors
Each refusal, what it means, and what to do. The request changed nothing.
400 Bad Request
What it means: The request failed a validate() schema, or an id in the path is not a valid id. path names the field.
What to do: Fix the field the body names in path (or read message) and send the request again. Nothing was changed.
{
"error": true,
"success": false,
"path": "string",
"message": "string"
}401 Unauthorized
What it means: The credential is missing, expired or not accepted here, or the caller's role has no grant for x-permission (refused with 401 too). The body is the plain text Unauthorized, or a JSON body with a code where the gate says why.
What to do: Send the credential this operation asks for (see Sign-in above), or sign in again if it expired. A valid credential is also refused when the role has no grant for the permission above.
Unauthorized429 Too Many Requests
What it means: A rate limit in x-rateLimit was reached. retryAfter and the Retry-After header say how many seconds until the window resets.
What to do: Wait the number of seconds in the Retry-After header (also retryAfter in the body), then retry. Slow down repeated calls.
{
"success": false,
"message": "string",
"reason": "rate_limited",
"retryAfter": 1
}Related
- All Me operations
- API reference: every operation, by tag
- Sign-in and credentials for the HTTP API
- How the HTTP API reports errors
- Make your first call
- Error codes: every
codethe API returns - OpenAPI: operation
me.billing.checkout.createin public-v1.json