Feedback on the proposed API pricing changes suggests we’ve hit the right note with developers. Here’s some info about when the new pricing takes effect and what it means for the bundled plans.

Number of transactions and transaction cost

Your plan will entitle you to a certain number of transactions per month – the bigger the plan the more transactions. And larger plans offer more value with volume discounting. The table below details the number of transactions each plan allows and the cost per transaction for each plan. 

If you need more than the Pro plan offers, talk to us about a custom plan.

We’ll update the PSMA Developer Portal in the coming months to show a transaction balance, rather than a credit balance. We’re also investigating how to enable the purchase of transaction blocks for when a developer consumes their balance for the month, and annual subscriptions with additional discounts. Your feedback on these options would be greatly appreciated. Please email us at [email protected]

Timing of pricing change 

The new pricing will come into effect on 9 May 2019. All customers on a bundled plan will be taking advantage of the better value pricing from 12pm on that day. You’ll also be able to access the Predictive Address API via your existing plan from then – it being bundled in with the other APIs. Those on the earlier free Predictive Address API plan will have until 9 August 2019 to decide whether to upgrade to the Starter plan or use the beta API. 

A hypothetical scenario… 

We thought it might be helpful to paint a picture of how a typical application would consume transactions on a given plan.

A paint-my-roof quote generator

You’re building a website solution that allows customers to obtain a quote for roof restoration. To generate the quote, the customer enters their address and collects information about the size of their home, if it has solar panels and its roof material. You know the quote process needs to account for homes that are too tall for a standard ladder and for some local government rules around site access. The website is expected to receive 4,000 customer enquiries a month.  

Using your bundled API plan

You can use the Predictive Address API to handle customer address entry with, say, 10 suggestions. 

Taking the GNAF ID returned by the Predictive Address API, you query the Buildings API to get the building area, footprint2d, solar panel, average eave height, roof material and roof complexity, and the Addresses API to get the local government area. 

You then use the information to build a reliable quote for the customer, with a visual outline of their home.

To get this data, you’d need approximately 8 transactions:

  • 10 suggestions at 0.1 transactions 
  • 1 address at 1 transaction  
  • 1 urban building at 6 transactions. 

At 4,000 quotes per month and 8 transactions per quote, your solution would need a ‘Plus’ plan - 32,000 transactions at $450 a month, with an average lead cost of 12 cents.

Tips to maximize value

With the new pricing structure, there are things you can do to get the most out of your plan. Here are a few tips: 

  1. Use the new ‘include all’ parameter. We’re no longer charging for each attribute, so make development life easier by including all attributes in a response. Link to API Reference
  2. Don’t use the attribute path to make multiple calls for the same address or building. When you request each attribute separately, you’ll be charged the full transaction cost per call. This will lead to a non-optimal spend of your developer balance. Link to API Reference
  3. When using the Predictive Address API, you’ll be charged for any successful suggestion returned. The API requires at least 4 alphanumeric characters before it returns a valid suggestion, but you can tailor your usage by only requesting suggestions when you feel you have enough information from your customer. Try only requesting a new suggestion at every second key-stroke or apply a cool-down wait of 100ms of no key-presses before triggering a suggestion. 
  4. Monitor the headers returned by the API to see how many transactions are being used in a call. We've introduced a new header called `x-attr-basicTransaction`. It’s returned on every call made to a PSMA API. If you have doubt about how much an API call is costing you, the header will show how many transactions are counted in the call. We also return this header in the beta API, which can be useful for testing, without consuming real paid transactions. Find out more about the PSMA Beta Program.

Feedback

If you’re a free plan customer and want to chat about your options, have questions generally or want to make a feature request, please reach out at [email protected] or use our Support Portal

Useful Links  

Developer Portal
Beta API document
Support Portal
GitHub repo