Postalgo API Plans and Limits
Status: Published
Version: 1.0
Effective date: 2026-08-05
Last updated: 2026-08-05
This page forms part of the Postalgo API Developer Agreement. It describes the current self-service API plan, eligibility rules, attribution, and usage limits.
Free API plan
The Free API plan is available for these uses:
| Use | Eligibility | Price |
|---|---|---|
| Personal | An individual acting personally on a non-commercial project and not for an employer, client, or other organisation | Free |
| Small commercial | An organisation, or a person acting for it, whose Customer Group has less than £1,000,000 in worldwide gross revenue during the previous 12 months | Free |
"Customer Group" means the organisation using or benefiting from the API and the entities that control it or are under common control with it. For work done for a client or customer, eligibility is based on that client or customer's Customer Group, not only the developer or agency making the request.
Revenue means gross revenue before costs, taxes, or distributions. If an organisation has existed for less than 12 months, use its gross revenue since it began operating.
Usage limits
The initial Free API plan includes:
- a burst limit of 10 requests per second
- a sustained limit of 60 requests per minute
- 50,000 requests per calendar month
Limits apply to the application and Customer Group as a whole. Creating more accounts, applications, or keys does not create additional allowances. Postalgo may aggregate related usage when applying a limit.
Batch endpoints should be used where available. A response may include headers
showing the remaining allowance or reset time. Requests over a limit may receive
429 Too Many Requests with a Retry-After header.
The Free API plan has no uptime guarantee or guaranteed support response time.
Required attribution
An application that displays or otherwise makes Postalgo metadata available to users must show this attribution in a reasonably visible place:
Music metadata provided by Postalgo Music
The attribution may appear on the relevant screen, in an application credits view, or on an about page where screen-level attribution would be impractical. It must remain easy for a user to find. It must not imply that Postalgo endorses the application.
When a separate agreement is required
Contact Postalgo before continuing API use if any of these applies:
- the Customer Group reaches £1,000,000 or more in worldwide gross revenue over the previous 12 months
- the application needs more than the Free API usage limits
- the intended use involves a bulk export or offline dataset
- the application will redistribute, resell, or provide access to a substantial part of the Postalgo Music database
- the application needs an uptime commitment, support commitment, or other service-level terms
A separate agreement may include different limits, fees, attribution, permitted uses, support, and service commitments. Access is not guaranteed merely because an applicant requests an agreement.
Plan eligibility changes
You must keep the information attached to your API application accurate. If a project becomes commercial, begins operating for an organisation, or crosses the revenue threshold, update the application and contact Postalgo before continuing use outside the Free API plan.
Changes to this page
Postalgo may update plans and limits to reflect operating cost, capacity, abuse, or product changes. We will publish the revised version and give reasonable notice before a material change affects an active, compliant application where practical. An enterprise agreement continues under its own change terms.
Contact
Plan and enterprise enquiries may be sent to:
Floffah
postalgo@floffah.dev