---
title: "API calls"
slug: "api-aufrufe-1"
updated: 2025-07-07T13:56:06Z
published: 2025-07-07T13:56:06Z
canonical: "help.frisbii.com/api-aufrufe-1"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.frisbii.com/llms.txt
> Use this file to discover all available pages before exploring further.

# API calls

## Basic API endpoints

The process of transferring purchases to Frisbii Media takes place via API requests.

The [API documentation](https://api.plenigo.com/#tag/App-Stores) documents all endpoints in connection with the use of in-app purchases.

Frequently used endpoints for standard processes are:

- [add purchase](https://api.plenigo.com/#tag/App-Stores/operation/addGooglePlaystorePurchase) - transfers data of an in-app purchase to Frisbii Media
- [get purchase](https://api.plenigo.com/#tag/App-Stores/operation/getGooglePlayStorePurchase) - queries transferred data of an identified in-app purchase from Frisbii Media
- [search purchase](https://api.plenigo.com/#tag/App-Stores/operation/searchGooglePlayStorePurchases) - searches the data of all in-app purchases in Frisbii Media
- [associate purchase](https://api.plenigo.com/#tag/App-Stores/operation/associateGooglePlaystorePurchase) - links the data of an in-app purchase in Frisbii Media with a customer account in Frisbii Media
- [dissociate purchase](https://api.plenigo.com/#tag/App-Stores/operation/dissociateGooglePlaystorePurchase) - removes the data of an in-app purchase in Frisbii Media from a customer account in Frisbii Media
- [verify purchase](https://api.plenigo.com/#tag/App-Stores/operation/verifyGooglePlaystorePurchase) - checks the data of an in-app purchase in Frisbii Media against the Google system, for example for validity

---

## Process for utilization

The standard process for the use of in-app purchases is described below.

1. every purchase that is to be used with Frisbii Media must be sent to the Frisbii Media API via an **add**
2. all purchases sent to Frisbii Media can be searched via **get** or **search**
3. If an already added purchase is to be linked to a known user, an **associate** is used
4. If a link is to be removed, a **dissociate** is used
5. a **verify request** is used to query whether the corresponding purchase is still valid, e.g. whether an App Store subscription is still active