aponitime™ pricing

API Keys & Nonces

An API key is needed to obtain a “nonce” (authentication token) from our authentication service. A nonce authorizes a browser to create and use customized aponitime™ pickers.

There is no charge to obtain an API key or nonce, but you must have an open account in good standing to create and/or use them.

An account, API key or nonce is not needed to use the default configuration (specifying only an input field selector).

Chargeable Requests

The complex logic behind aponitime™ pickers is handled by a proprietary SaaS (software-as-a-service).

Each message to the service requesting that a customized picker be created or updated is called a “chargeable request.”

Pickers that use the default configuration do not generate chargeable requests.

Chargeable requests must be purchased in advance; your purchase helps offset the cost to maintain the service and fund future development.

There is no need to purchase chargeable requests if you only use the default configuration!

Pricing for chargeable requests is currently as follows (USD) and subject to change without notice:

quantityprice
0$1
0$4
0$49
0$450

Chargeable requests can be purchased from your account page.

Purchased chargeable requests do not expire and are non-refundable.

Requests made against an empty account may fail. We can send you notifications when your allotment is running low, but you should monitor your account to help avoid unexpected failures.

How Many Is Enough?

The more a user interacts with a customized picker, the more chargeable requests it will generate.

A typical date or time picker generates approximately ten (10) chargeable requests from the time it is created until the user confirms their selection.

To determine the approximate number of chargeable requests your picker(s) will generate:

  1. In your browser, open the developer tools and select Network.
  2. Load your web page and interact with your picker(s) like a typical user.
  3. In the Network panel, expand the websocket connection(s) to the service (typically by double-clicking) and examine the Messages panel.
  4. Tally the number of uploaded request messages (with a green up-arrow) that begin with 7, 8 or 9 (these are typically counted as chargeable requests). Do not include downloaded response messages (with a red down-arrow) or messages that begin with another value.

Lower Your Costs!

To generate fewer chargeable requests, reduce the effort it takes to choose the right values! Here are two easy hacks:

  • Increase the height of the wheels by passing the zWsetHeight option to fdnCreate(), or specifying the H argument with your template tags.
  • Initialize each wheel's value to the most-likely choice, using the vInit instant segment property. If you’re not sure which choice is most likely, use the middle choice.