Skip to content

Commit fb62ffe

Browse files
Update getting-started.mdx
1 parent 8fc9deb commit fb62ffe

File tree

1 file changed

+3
-13
lines changed

1 file changed

+3
-13
lines changed

docs/reporting/getting-started.mdx

+3-13
Original file line numberDiff line numberDiff line change
@@ -2,17 +2,7 @@
22
sidebar_position: 1
33
---
44

5-
# Getting started
5+
:::caution Closed
66

7-
Before you start it is important to check the API documentation to ensure that the data supplied through the API is relevant for your need. You'll find it [here](/api/reporting)
8-
9-
## Authenticate to the API
10-
11-
Next step is to determine which security solution you want to use. We are providing two different options for authentication.
12-
13-
- [API keys](/docs/reporting/authentication/api-key): This is a simple solution aimed at merchants integrating on their own behalf. They are used to get unlimited access to resources in your merchant account. These are retrieved through the MobilePay Portal. If you choose this option you simply need to [retrieve the API key](/docs/reporting/authentication/api-key#get-an-api-key) from the MobilePay portal to get started.
14-
- [OAuth](/docs/reporting/authentication/open-id): This is aimed at larger merchants or integrators integrating on behalf of one or more merchants. It is used to get authenticated and scoped access to any MobilePay merchant account. Use them when your application will access resources on behalf of multiple MobilePay merchant accounts, i.e. you are an integrator. If you choose this option please contact [email protected] to get started.
15-
16-
## Production
17-
18-
The reporting API consists of only GET endpoints where you can retrieve transaction and transfer details. Therefore we do not require any sandbox test or verification in order to use this product in production.
7+
It is no longer possible to use the Reporting API. The product have been replaced with [Report API](https://developer.vippsmobilepay.com/docs/APIs/report-api/)
8+
:::

0 commit comments

Comments
 (0)