Freemius API (1.0)

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.

  • Manage products.
  • Manage license verifications.
  • Create custom integration with your SaaS.

If you're using Freemius for a WordPress product, please check out our official SDK.

Browse Tutorials and Guides.

Bearer Token Auth

Freemius API supports Bearer Token authentication for product-specific operations.

To retrieve your API token:

  1. Go to the Freemius Developer Dashboard.
  2. Open the Settings page of the relevant product.
  3. Click on the API Token tab.
  4. Copy the API Bearer Authorization Token from the UI.

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.

Other Scopes and Authentication

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:

  • Product Scope: /products/{product_id}/payments.json.
  • Developer Scope: /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:

  • User Scope: /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:

  • Update Plan: POST /developers/{developer_id}/products/{product_id}/plans/{plan_id}.json
  • Create Plan: POST /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.

Download OpenAPI description
openapi.yaml
Overview
URL

https://freemius.com

Freemius Support

support@freemius.com

License

Proprietary

Terms of Service

Languages
Servers
Production API

https://api.freemius.com/v1/

Local development API

http://api.freemius-local.com:8080/v1/

Mock server

https://docs.freemius.com/_mock/api/

Products

All operations which can be done on a product.

Operations

Developers

All operations which can be done from on a developer.

Operations

Subscriptions

All operations associated to a subscription.

Operations

Users

All operations which can be done on a user belonging to a store or a product.

Operations

Licenses

All operations which can be done on a license belonging to a store or a product.

Operations

Coupons

All operations which can be done on a coupon belonging to a store or a product.

Operations

Carts

All operations which can be done on a cart belonging to a store or a product.

Operations

Payments

All operations associated to a payment.

Operations

Installations

Operations related to the installation of a product.

Operations

Trials

Operations related to a trial license of a product.

Operations

Addons

Operations related to an addon of a product.

Operations

Plans

Operations related to plans, pricings and features of a product.

Operations

Events

Operations related to events of a store or product.

Operations

Retrieve an event

Request

Retrieve a specific event by its ID. For instructions on creating webhook listeners, see the documentation.

Path
product_idinteger(int64)>= 1required

The ID of the product.

Example: 1234
event_idinteger(int64)>= 1required

The ID of the event.

Example: 1234
Query
fieldsstring

Comma separated list of fields to return in the response. If not specified, all fields are returned.

Example: fields=id,name,slug
curl -i -X GET \
  'https://api.freemius.com/v1/products/1234/events/1234.json?fields=id%2Cname%2Cslug' \
  -H 'Authorization: Bearer <YOUR_AccessToken_HERE>'

Responses

The retrieved event.

Bodyapplication/json
idstring(int64)>= 1

The unique identifier of the entity.

Example: "123456"
createdstring(date-time)

The date and time the entity was created, under UTC timezone.

Example: "2025-01-01 00:00:00"
updatedstring or null(date-time)

The date and time the entity was updated, under UTC timezone. If null then the entity was never updated since its creation.

Example: "2025-01-01 00:00:00"
typestring

The type of event. See our documented list of the available event types.

Example: "license.activated"
developer_idstring(int64)>= 1

The ID of the developer.

Example: "1234"
plugin_idstring or null(int64)>= 1

The ID of the product the entity belongs to. Null means it has not been associated with a product yet.

Example: "123456"
user_idstring or null(int64)>= 1

The ID of the user the entity belongs to. If NULL then still not associated to any user.

Example: "123456"
install_idstring or null(int64)>= 1

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.

Example: "123456"
dataany or null

The details of the triggered event. This can be a string showing ID of the associated entity, an object with additional information of the event, or array of objects.

event_triggerstring

The type of trigger for the event.

Enum"system""developer""plugin""user""install"
Example: "system"
process_timestring or null(date-time)

The time the event was processed. If it is null, the event is pending.

Example: "2025-01-01 12:00:00"
objectsobject

A map of related objects keyed by their type or ID, such as Payment, User, Install, or License.

Example: {"user":{"id":"1234567","email":"user@example.com","first":"Joe","last":"Doe","is_verified":true},"install":{"id":"1234567","plugin_id":"12345","user_id":"1234567","url":"https://example.com","plan_id":"12345"},"license":{"plugin_id":"12345","user_id":"12345","plan_id":"12345","pricing_id":"12345","quota":10,"expiration":"2025-10-01 10:11:46","id":"1234567","created":"2025-01-01 01:11:46","updated":"2025-01-01 01:11:46"},"payment":{"subscription_id":"12345","gross":14.99,"gateway_fee":0.41,"vat":1.52,"is_renewal":true,"type":"payment","user_id":"12345","install_id":"12345","plan_id":"12345","pricing_id":"12345","license_id":"12345"}}
Response
application/json
{
  "id": "123456",
  "created": "2025-01-01 00:00:00",
  "updated": "2025-01-01 00:00:00",
  "type": "license.activated",
  "developer_id": "1234",
  "plugin_id": "123456",
  "user_id": "123456",
  "install_id": "123456",
  "data": null,
  "event_trigger": "system",
  "process_time": "2025-01-01 12:00:00",
  "objects": {
    "user": { … },
    "install": { … },
    "license": { … },
    "payment": { … }
  }
}

List all events

Request

Retrieve a list of events for a specific product. Supports filtering by type, state, and pagination. See the documentation for instructions on creating a webhook to listen for events.

Path
product_idinteger(int64)>= 1required

The ID of the product.

Example: 1234
Query
typestring

Filter events by type string or event name, such as license.created. See the documentation for a list of available event types.

statestring

Filter events by state: 'pending', 'processed', 'error', or 'canceled'.

Enum"processed""pending""canceled""error"
countinteger[ 1 .. 50 ]

The number of records to return.

Default 25
Example: count=10
offsetinteger>= 0

The number of records to skip before starting to return records. Default is 0.

Default 0
Example: offset=10
fieldsstring

Comma separated list of fields to return in the response. If not specified, all fields are returned.

Example: fields=id,name,slug
curl -i -X GET \
  'https://api.freemius.com/v1/products/1234/events.json?count=10&fields=id%2Cname%2Cslug&offset=10&state=processed&type=string' \
  -H 'Authorization: Bearer <YOUR_AccessToken_HERE>'

Responses

A collection of events.

Bodyapplication/json
eventsArray of objects(EventLog)
Response
application/json
{
  "events": [
    { … }
  ]
}

Reviews

Operations related to reviews of a product.

Operations

Deployments

Operations related to version deployments and retrieval.

Operations