Postalgo API Developer Agreement
Status: Published
Version: 1.0
Effective date: 2026-08-05
Last updated: 2026-08-05
This API Developer Agreement governs access to and use of the Postalgo API. It supplements the Postalgo Terms of Service and includes the current API Plans and Limits.
In this agreement, "you" means the person accepting it and, where that person acts for an organisation, that organisation. "Application" means the product or service registered for an API key. "API Data" means metadata returned by the Postalgo API, excluding third-party material that Postalgo does not have the right to license.
1. Acceptance and authority
You must accept this agreement before Postalgo issues an API key. If you act for an organisation, you confirm that you have authority to bind it and that the registration information identifies it accurately.
Each Application must be registered under the person or organisation that operates it. Keys issued for personal use may not be used for an employer, client, or other organisation unless the registration and plan eligibility are updated first.
2. API licence
While your account and key remain active and you comply with this agreement, Postalgo grants you a limited, non-exclusive, non-transferable, non-sublicensable licence to:
- request API Data for the registered Application
- cache the records reasonably needed to operate that Application
- reproduce and display those records to the Application's users
- use API Data in a commercial Application when the Customer Group remains eligible for its plan
The licence applies only to rights Postalgo controls and only for the use described in the API registration. It does not license music, audio, artwork, articles, trademarks, personal information, or third-party content merely because the API links to or describes that material.
3. Ownership and reserved rights
Postalgo and its licensors retain their rights in the API, its design, and the Postalgo Music database. Postalgo reserves any copyright, database rights, and other rights it holds in the selection, verification, arrangement, and presentation of the database.
Individual facts may not be protected by copyright. This agreement does not claim ownership of facts you obtain independently from a lawful source. It does govern access through Postalgo, use of API Data under the licence above, and your contractual use of an API key.
An API key does not grant ownership of API Data or a right to obtain a copy of the database.
4. Attribution
You must provide the attribution required by the current API Plans and Limits. You may not remove source or rights information supplied with a response.
Attribution must not suggest that Postalgo sponsors, certifies, or endorses you or the Application.
5. Permitted caching
You may keep a reasonable cache of records that the Application actually uses. Caching should reduce repeated requests and preserve existing user-facing content during a temporary outage.
Caching must not be used to enumerate the API, build a substitute catalog, or avoid a plan limit. Where a response identifies data as temporary, private, or subject to a shorter retention rule, you must follow that rule.
6. Prohibited use
You must not:
- systematically enumerate the API or collect records for the purpose of reconstructing all or a substantial part of the Postalgo Music database
- publish, sell, sublicense, or redistribute all or a substantial part of API Data as a dataset or competing metadata service
- use repeated requests for small portions where the combined purpose or effect is bulk extraction
- scrape Postalgo websites instead of using the authorised API
- bypass or evade authentication, technical restrictions, rate limits, monthly allowances, or plan eligibility rules
- divide one Application or Customer Group across accounts or keys to obtain extra allowances
- share, sell, or expose an API key
- use the API for unlawful, deceptive, infringing, or harmful activity
- test the security of the API without written permission
- use API Data to imply a false association with Postalgo or another person
Bulk access, dataset redistribution, and higher-volume use require a separate written agreement.
7. Plans and commercial eligibility
Your use is subject to the current API Plans and Limits. You must provide accurate information about the Application, whether you act personally or for an organisation, and the Customer Group's revenue eligibility.
You must update that information when it changes. If the Application ceases to qualify for the Free API plan, you must contact Postalgo and obtain a suitable agreement before continuing use outside that plan.
Postalgo may apply limits across related accounts, Applications, keys, or organisations where they form one Customer Group or serve the same project.
8. API keys and security
Keep each API key confidential and use reasonable security measures to prevent unauthorised access. Do not place a secret key in public source code or software where an end user can recover it.
Tell us promptly if a key may have been exposed. We may rotate, restrict, or revoke a key to address security, abuse, legal risk, inaccurate registration, or breach of this agreement.
9. Application responsibility and privacy
You are responsible for the Application, its users, and compliance with laws that apply to it. You must provide your own terms and privacy information where required. Do not send personal information to the API unless an endpoint expressly requests it and you have a lawful reason to provide it.
You must not use API Data or combine it with other information in a way that violates privacy, publicity, copyright, trademark, or other rights.
10. Availability and changes
The self-service API is provided "as is" and "as available" without an uptime or support guarantee. Endpoints may be deprecated or replaced. Where practical, Postalgo will document material changes and provide a reasonable migration period for a stable API version.
Postalgo may introduce emergency limits or suspend requests immediately to protect security, service availability, or other users.
11. Suspension and termination
You may stop using the API and revoke your keys at any time. Postalgo may suspend or terminate API access for breach, security risk, material registration inaccuracy, non-payment under a separate agreement, or where required by law.
When this agreement ends, you must stop making requests and delete cached API Data within a reasonable period. You may retain backups for their normal rotation period and minimal snapshots already attached to persistent user content, provided you continue to follow the attribution, security, and prohibited-use provisions.
Sections concerning ownership, restricted bulk use, retained data, liability, and rights already accrued continue after termination.
12. Liability
Postalgo does not promise that API Data is complete, accurate, or suitable for a particular purpose. You are responsible for how the Application uses and presents it.
To the extent permitted by law, Postalgo is not responsible for indirect or unforeseeable loss, lost profits, loss caused by third-party material, or loss caused by use outside this agreement.
Nothing in this agreement excludes or limits liability where doing so would be unlawful, including liability for fraud or for death or personal injury caused by negligence. Nothing in this agreement reduces mandatory consumer rights.
13. Changes to this agreement
Postalgo may update this agreement as the API changes. We will publish the new version and give reasonable notice of material changes. We may require you to accept a material revision before using or receiving another API key.
14. Contact
API and licensing enquiries may be sent to:
Floffah
postalgo@floffah.dev