Football API pricing: plans, daily allowances and overage billing

The monthly subscription price pays for the plan's included daily usage, not a pool you can spend at any time during the month. A Starter account making 6,000 successful requests today uses 5,000 included requests and creates 1,000 metered extras. Making only 2,000 tomorrow does not offset those extras, because the daily inclusion has no rollover.

Additional successful requests on a paid metered subscription cost €0.002 each. One thousand extra requests cost €2.00, and ten thousand cost €20.00. Overage is aggregated before rounding the invoice line to cents and billed monthly in arrears on the EUR subscription invoice. Failed, invalid and denied requests are not billed.

Use the usage dashboard to distinguish attempted requests from successful billable delivery. Successful cache hits served by FootballAPI.net count as requests; a page view served entirely from your own application cache does not make another API call. No free trial is currently offered.

You can create an account, generate and rotate API keys, read all documentation, download the customer guide and the OpenAPI specification, and use schema mode in the dashboard playground, which returns field documentation without records. You can also contact support about your use case.

Record-bearing requests require active account access, a valid key and a published endpoint that your plan can use. Starter league selection and specialist live-service activation remain relevant even after a subscription is active. Schema inspection is not proof that a data request will be authorised.

Starter covers five saved leagues. Use the league-selection controls to inspect the current choices and replacement lock before planning a competition change. Growth and Pro cover all available package leagues, but the presence of a league does not guarantee historical depth, photos, predicted line-ups or every optional event.

Some live services have separate setup requirements, including application IP approval through FootballAPI.net. Ball tracking also requires a supported plan and an actual live connection. Ask support about the precise service and competitions you need; a subscription does not silently remove these activation requirements.

Use the signed-in billing page to review the plan, current checkout availability and subscription state. Checkout is designed to stay within FootballAPI.net using Stripe's embedded payment components; card information is handled by Stripe, not by an API feed request. Confirm the displayed total before submitting payment and use the resulting account state rather than a button click as evidence that access is active.

If a payment appears incomplete or your account does not reflect a completed purchase, do not repeatedly submit it. Contact support with the approximate time and non-sensitive invoice reference. Never send card details, secret keys or a full API key through a support message.

Build with caching so request volume follows your refresh schedule, not visitor traffic. Three endpoint requests every minute for ten hours produce 1,800 calls per day before detail requests or other workers. If one shared backend performs those calls, a thousand readers can reuse the same snapshot. If each reader calls the API independently, the budget changes completely.

Keep per-second behaviour conservative: spread requests and honour Retry-After, so whatever limit is set, you are comfortably within it.

Publishing a monthly price does not resolve every operational question. Customers also need clear included usage, the cost of additional requests, an understood tax treatment and coverage permissions. Our included allowances reset at midnight UTC; a shared account safety limit of 100 requests per second still applies when paid overages are active. Additional successful requests cost €0.002 each and are invoiced monthly in arrears. There is no free trial. We distinguish published terms from live service activation so you can plan an integration without assuming that registering an account has started a subscription. Keep the published price list and a separate list of required service activations in your procurement notes.

Treat the public endpoint catalogue as a list of available operations, not an uptime score. A live-score REST snapshot and a ball-tracker stream are different products. Validate the fields and competitions your application requires, and keep a last-good snapshot so a temporary request failure does not erase the page.

The business is based in the UK and is not VAT registered; no VAT is currently charged. Do not interpret that as a VAT registration number, a tax invoice showing VAT or a statement about another country's tax rules. Review the current terms and data licence for permitted display, caching and redistribution, and ask support about any required contractual documents.

Use the pricing page for the public offer and the dashboard for your account's subscription and usage state. This article explains the calculation; it is not a real-time payment-status monitor. Your account does not become a paid subscription automatically because you read a guide, create a key or inspect an example response.

Procurement teams should record the required competitions, historical seasons, refresh intervals and permissions before selecting a plan. Keep a price calculation separate from any requested service-level commitment or data processing agreement. A published monthly price does not create a latency guarantee or confer rights to resell a feed.

If your organisation cannot proceed without those documents, tell support your timeline. We would rather say plainly that something is not ready than offer a commitment we cannot keep.

Evaluate schema mode first, then test authorised data requests against the exact leagues your product will use. Keep examples redacted, record missing fields and compare observed successful request volume with your forecast before increasing the refresh schedule.

Security and identifiers matter whichever plan you select. Keep X-API-Key or bearer credentials on your backend, preserve competition and match identifiers, and never use club names as database keys. Read the media documentation before exposing image URLs; a team crest and a competition logo are not interchangeable services.

Check the response status before parsing, bound retries and honour Retry-After on 429 responses. Paid overages allow additional successful daily usage but do not waive the account safety limit, specialist activation or data-licensing restrictions. Those controls serve different purposes.

When comparing providers, compare like with like: the same competitions, feeds and refresh needs. A low headline price with tight limits can cost more in practice than a higher price with limits that suit your schedule.

For access requests or questions about commercial terms, use the support page in your dashboard or the contact page. Describe your product, competitions and expected refresh schedule so we can respond usefully.