Welcome to the Freemius API Documentation!
You can use our API to access Freemius API endpoints, which can get information on various aspects of Freemius.
If you're using Freemius for a WordPress product, please check out our official SDK.
Freemius API supports Bearer Token authentication for product-specific operations.
To retrieve your API token:
Use this token by including it in the Authorization
header of your API requests:
Authorization: Bearer {api_token}
Bearer tokens are scoped to a specific product. This means they can only be used with endpoints under the /products/{product_id}/
namespace. For example:
GET /products/12345/users.json
Authorization Bearer {api_token}
Requests to endpoints outside the product scope will result in an authorization error.
The Freemius API is organized around different scopes, based on the top-level entity of the operation:
For example, let's say you want to list all payments of a product. This operation can be done in several scopes:
/products/{product_id}/payments.json
./developers/{developer_id}/products/{product_id}/payments.json
.On the other hand, if a user would want to list their payment, then endpoint will be scoped to the user:
/users/{user_id}/payments.json
.Some operations can be done from a particular scope only. For example only a developer can update a plan of a product or create a new plan. So the following operations will work:
/developers/{developer_id}/products/{product_id}/plans/{plan_id}.json
/developers/{developer_id}/products/{product_id}/plans.json
If you try to perform the same operation on a product scope, it will return an error. The scopes provides a way to control access and permissions for different entities in the Freemius ecosystem.
Currently, Bearer Token authentication is supported for product scope only. If you need access to endpoints in others scopes, use the secret-key based authentication with the following SDKs:
For most use cases, managing your products, licenses, and customers through the Developer Dashboard or Customer Portal provides all the necessary capabilities.
https://api.freemius.com/v1/
https://docs.freemius.com/_mock/api/
https://api.freemius.com/v1/products/{product_id}/payments/{payment_id}.json
https://docs.freemius.com/_mock/api/products/{product_id}/payments/{payment_id}.json
curl -i -X GET \
'https://api.freemius.com/v1/products/1234/payments/1234.json?fields=id%2Cname%2Cslug' \
-H 'Authorization: Bearer <YOUR_AccessToken_HERE>'
Retrieve a specific payment.
The ID of the installation or site the entity is associated with, a null
value means it has not been associated with an installation yet.
The ID of the pricing associated with the entity.
The ISO 3166-1 alpha 2 two-letter country code associated with the entity.
The business VAT number (EU or UK territories) or other tax ID (for example Sales Tax ID for the US).
The ID of the coupon associated with the entity.
The source of the migration data. To get support migrating from other platform please see our documentation.
0
- Freemius1
- Other2
- Easy Digital Downloads (EDD)3
- WooCommerce (WC)4
- Rating Widget5
- Gumroad6
- CodeCanyon7
- ThemeForest8
- AppSumo9
- SendOwl10
- WHMCS11
- Lemon SqueezyThe gateway used for the purchase. The gateway will be set to null
when purchasing a product with a 100% discount.
The environment the entity belongs to. 0 means it belongs to the production environment, 1 means it belongs to the sandbox environment.
The date and time the entity was created, under UTC timezone.
The date and time the entity was updated, under UTC timezone. If null
then the entity was never updated since its creation.
The ID of the subscription associated with the entity.
The ID of the payment that this payment is bound to, in case of a refund or chargeback/dispute.
The fee that the gateway took for processing this payment.
The actual tax amount. It could be any kind of tax, not necessarily VAT. For example we support US Sales Tax.
{ "user_id": "123456", "install_id": "123456", "plan_id": "123456", "pricing_id": "123456", "license_id": "123456", "ip": "0.0.0.0", "country_code": "us", "zip_postal_code": "92710", "vat_id": "GB12345678", "coupon_id": "123456", "user_card_id": "12345", "source": 0, "plugin_id": "123456", "external_id": "abcde12345", "gateway": "string", "environment": 0, "id": "123456", "created": "2025-01-01 00:00:00", "updated": "2025-01-01 00:00:00", "subscription_id": "123456", "gross": 2075.45, "bound_payment_id": "123456", "gateway_fee": 2.99, "vat": 1.24, "is_renewal": false, "type": "payment" }
Retrieve the payment collection associated with the product.
You search and/or filter payments with these parameters:
search
- You can search by payment_id
, external_payment_id
, or user_email
. It can be a number or string.user_id
- If you are looking to list all payments for a specific user use this.billing_cycle
- Filter payments by billing cycle. 0
means lifetime payments.currency
- Filter payments by currency.coupon_id
- Filter payments by coupon ID.filter
- Filter payments by different types: all
, refunds
, not_refunded
, disputed
, won_disputes
, chargebacks
.Please see the parameters in the responses body for more information.
Filter payments by different types
The end of the date range in YYYY-MM-DD HH:MM:SS format
The start of the date range in YYYY-MM-DD HH:MM:SS format
The number of records to skip before starting to return records. Default is 0.
https://api.freemius.com/v1/products/{product_id}/payments.json
https://docs.freemius.com/_mock/api/products/{product_id}/payments.json
curl -i -X GET \
'https://api.freemius.com/v1/products/1234/payments.json?billing_cycle=1&count=10&coupon_id=123456¤cy=usd&extended=false&fields=id%2Cname%2Cslug&filter=all&from=2025-08-01%2000%3A00%3A00&offset=10&search=string&search_user_id=123456&to=2025-08-01%2000%3A00%3A00' \
-H 'Authorization: Bearer <YOUR_AccessToken_HERE>'
{ "payments": [ { … } ], "discounts": [ { … } ] }