Developer tools integration
Read-only reporting APIAPI integration
Use the private adslink.io reporting API to give an authorized POS client scoped access to saved advertising data.
See the reporting experience
API dashboard preview
An illustrative view of the available reporting experience. All names and values below are synthetic; no account is connected by this preview.
- Access
- Read only Sample
- Scope
- Saved reports Sample
- Currency
- AED Sample
- Rows
- 3 sample Sample
Saved report response
{ "currency": "AED", "rows": 3,
"data": [{ "account": "Sample account A",
"spend": "500.00", "clicks": "750" }] }Access scope
- Reports
- Authorized only
- Credentials
- Server-side
- Write actions
- Not supported
Sample report rows
| Account | Spend | Clicks | Conversions |
|---|---|---|---|
| Sample account A | AED 500 | 750 | 20 |
| Sample account B | AED 300 | 450 | 12 |
| Sample account C | AED 200 | 300 | 8 |
API reporting in your workspace
Connect your own reporting consumer to data already saved in adslink.io. The POS integration creates a scoped credential with account access, reporting permissions and limits that you configure. This API is intended for reading authorized reports; it is not an ad-management API or an arbitrary external-data import endpoint.
What you can report on
- Scoped access to supported saved account and reporting resources.
- Explicit account selection, reporting scopes and configurable history limits.
- Token rotation and revocation controls for the authorized client.
Before you begin
- Permission to manage POS Integration in the intended workspace.
- A trusted client that can protect a bearer token on its server.
- A defined account scope and reporting history appropriate to the client’s purpose.
How to connect API
Open POS Integration
Use POS Integration in the authenticated workspace. Review the endpoint documentation shown by the app.
Limit the access
Choose the reporting scopes, account selection and available expiry or access restrictions that your client actually needs.
Create the client credential
Generate the token and copy the one-time value into the client’s protected server configuration. Do not expose it in browser code or a public link.
Read and maintain access
Use the app’s API examples to request saved reporting data. Monitor access, respect reporting limits and rotate or revoke the token when the client no longer needs it.
Availability and reporting limits
API access does not authorize campaign creation, budget edits or billing changes. A token can read only the resources and reporting scope allowed by its current configuration.
The Connect link opens the authenticated app. Sign in and choose the intended workspace; provider setup, permissions and plan capacity still apply.
API integration FAQs
Can this API import another platform into adslink.io?
The current POS reporting API reads supported saved data. A new inbound provider integration would need a separate implementation.
Where do I find the endpoint and token?
Open the protected POS Integration page. It shows current endpoint guidance and lets an authorized user create or manage the credential.