Discover/puntodeventa API
live

puntodeventa APIpuntodeventa.digital ↗

Retrieve subscription plan names, prices, billing periods, and plan codes from puntodeventa.digital's public pricing page via a single API endpoint.

Endpoint health
verified 1h ago
list_plans
1/1 passing latest checkself-healing
Endpoints
1
Updated
2h ago

What is the puntodeventa API?

The puntodeventa.digital API exposes 1 endpoint — list_plans — that returns every subscription plan listed on the site's public pricing section, delivering up to 7 structured fields per plan including name, price, currency symbol, billing period, plan code, and a featured flag. It also surfaces any site-wide pricing note shown above the plan cards, making it straightforward to mirror or monitor the pricing catalog programmatically.

This call costs1 credit / call— charged only on success
Try it

No input parameters required.

→ api.parse.bot/scraper/d0eee488-9402-49ed-9fe3-331035aafe3e/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/d0eee488-9402-49ed-9fe3-331035aafe3e/list_plans' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK · recommended

Typed, relational, agent-ready

A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.

  • Fully typed · autocompletes
  • Objects link to objects
  • Typed errors & pagination

Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:

uv add parse-sdk
uv run parse init
uv run parse add --marketplace puntodeventa-digital-api

uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.

"""Walkthrough: fetch and display subscription plans from puntodeventa.digital."""
from parse_apis.puntodeventa_digital_api import PuntoDeVentaDigital, ParseError

client = PuntoDeVentaDigital()

# Retrieve the full pricing overview (includes the site-wide note).
try:
    pricing = client.pricing.get()
except ParseError as e:
    # The site structure may change; surface the wire error code.
    print("Extraction failed:", e.code)
    raise
print("Note:", pricing.note)
print(f"{pricing.total} plans available\n")

# Iterate individual plans with a total-items cap.
for plan in client.plans.list(limit=10):
    badge = f" [{plan.badge}]" if plan.badge else ""
    print(f"{plan.name}: {plan.price_display} {plan.billing_period}{badge}")
    print(f"  {plan.description}")

print("\nexercised: pricing.get / plans.list")
All endpoints · 1 totalmissing one? ·

Returns every subscription plan advertised on the public pricing section of the site, one record per plan card, in the order the site lists them. Each record carries the plan name, its short description, the numeric price with the currency symbol as shown on the page (the site is Mexican-Spanish and displays a bare $ symbol; the currency is not stated explicitly), a display string, the billing period text (e.g. 'al mes'), the site's plan code taken from the sign-up link, and whether the plan is highlighted with a badge. One page request, no parameters, no pagination. A page without the plans section returns an extraction error rather than an empty list.

Input

No input parameters required.

Response
{
  "type": "object",
  "fields": {
    "note": "site-wide note shown above the plans, or null",
    "plans": "array of plan records: name, description, currency_symbol, price (number), price_display, billing_period, plan_code, featured (boolean), badge (string or null when the plan has no badge)",
    "total": "integer count of plans returned"
  },
  "sample": {
    "data": {
      "note": "Todos los planes incluyen las funciones de la plataforma, el panel de configuración y actualizaciones.",
      "plans": [
        {
          "name": "Prueba",
          "badge": null,
          "price": 500,
          "featured": false,
          "plan_code": "15d",
          "description": "Para conocer la plataforma.",
          "price_display": "$500",
          "billing_period": "por 15 días",
          "currency_symbol": "$"
        },
        {
          "name": "Anual",
          "badge": "MÁS ELEGIDO",
          "price": 1300,
          "featured": true,
          "plan_code": "ano",
          "description": "Mayor continuidad para tu negocio.",
          "price_display": "$1,300",
          "billing_period": "al año",
          "currency_symbol": "$"
        }
      ],
      "total": 4
    },
    "status": "success"
  }
}

About the puntodeventa API

What the API Returns

The list_plans endpoint returns the full set of subscription plans advertised on puntodeventa.digital's pricing page, preserving the order the site displays them. Each plan record includes: name (the plan's display title), description (the short tagline shown on the card), currency_symbol (e.g. $ or MXN as shown on-page), price as a numeric value, price_display as the formatted string, billing_period (monthly, annual, etc.), plan_code (a machine-readable identifier), and a boolean featured flag indicating whether the plan is highlighted as a recommended option.

Response Structure

Beyond the plans array, the response includes a top-level note field that captures any site-wide message displayed above the plan listing — useful for detecting promotional notices or caveats — and a total integer confirming the count of plan records returned. The endpoint takes no input parameters; a single call retrieves the complete current plan catalog.

Coverage and Freshness

Data reflects the plans currently visible on the public pricing section of puntodeventa.digital. If the site updates plan names, adds tiers, changes prices, or removes plans, a fresh call to list_plans will reflect those changes. The API does not cache a historical snapshot; each call returns the live state of the pricing page.

Reliability & maintenanceVerified

The puntodeventa API is a managed, monitored endpoint for puntodeventa.digital — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when puntodeventa.digital changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.

This isn't an official puntodeventa.digital API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.

Last verified
1h ago
Latest check
1/1 endpoint passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Monitor puntodeventa.digital plan prices over time by polling list_plans and logging the price field
  • Detect when a new plan tier is added by tracking changes in the total count across calls
  • Identify which plan carries the featured flag to understand the site's recommended upsell
  • Extract plan_code values for use in downstream billing integrations or comparison tools
  • Surface the site-wide note field in a pricing aggregator to capture promotional messaging
  • Build a competitive pricing dashboard that tracks billing_period and price_display across POS software vendors
  • Alert on pricing page changes by diffing the plans array between scheduled API calls
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo2005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min
Team$300/mo20,000300 req/min
Company$1,000/mo100,000500 req/min

Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does puntodeventa.digital offer an official developer API?+
puntodeventa.digital does not publish a documented public developer API. This Parse API provides structured access to the data available on their public pricing page.
What does the `list_plans` endpoint return for each plan?+
Each record in the plans array includes name, description, currency_symbol, price (numeric), price_display (formatted string), billing_period, plan_code, and a featured boolean. The response also contains a top-level note (or null) and a total plan count.
Can I filter plans by billing period or price range?+
The list_plans endpoint takes no input parameters and returns all plans in a single response. Filtering by billing_period, price, or featured status needs to be done client-side on the returned plans array. You can fork this API on Parse and revise it to add server-side filtering parameters.
Does the API return feature lists or included modules for each plan?+
Not currently. The API covers plan-level fields: name, description, price, billing period, plan code, and featured status. Detailed per-plan feature breakdowns or module inclusions are not part of the current response. You can fork this API on Parse and revise it to add an endpoint that captures per-plan feature lists.
Is historical pricing data available through this API?+
The API returns the current live state of the pricing page; it does not store or expose historical pricing records. Each call to list_plans reflects what is shown on the site at that moment. You can fork this API on Parse and revise it to persist snapshots to your own datastore for historical tracking.
Page content last updated . Spec covers 1 endpoint from puntodeventa.digital.
Related APIs in EcommerceSee all →