canonical: https://jentic.com/apis/swaggerhub.jensmostaert3/api-of-the-adshot-core-service

# Jensmostaert3 API of the Adshot Core service

This is the API definition for the Adshot Core service. The API exposes 34 endpoints.

## For AI agents

Programmatically list / search all gamers., retrieve details of a specific gamer.. Covers 34 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- List / search all Gamers.
- Retrieve details of a specific Gamer.
- Update Gamer profile.
- Query and filter API of the Adshot Core service
 records by parameters
- Monitor API of the Adshot Core service
 operational status and events

## Use cases

### Developer Tools Operations

Use the API of the Adshot Core service
 to perform developer tools operations programmatically. The API provides 34 endpoints covering core functionality including list / search all gamers., retrieve details of a specific gamer., update gamer profile..

Example prompt: Call GET `/v1/gamers` to list / search all gamers.

### Automated Operations on Gamers Management

Automate operations on gamers operations by combining multiple API of the Adshot Core service
 endpoints. Agents can retrieve details of a specific gamer. and then update gamer profile. in a single workflow.

Example prompt: Call GET `/v1/gamers/{id}` to retrieve details of a specific gamer., then verify the result

### AI Agent Integration via Jentic

AI agents discover and call API of the Adshot Core service
 endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'list / search all gamers.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/gamers` | List / search all Gamers. |
| GET | `/v1/gamers/{id}` | Retrieve details of a specific Gamer. |
| PATCH | `/v1/gamers/{id}` | Update Gamer profile. |
| GET | `/v1/gamer` | Retrieve the Gamer resource owned by the authenticated user. |
| PATCH | `/v1/gamer` | Update Gamer profile owned by the authenticated user. |
| GET | `/v1/advertisers` | List / search through all Advertiser profiles |
| GET | `/v1/advertisers/{id}` | Retrieve details of a specific Advertiser |
| PATCH | `/v1/advertisers/{id}` | Update a specific Advertiser |

## Key resources

- **Operations on Gamers** — Gamer Controller
- **Operations on Advertisers** — Advertiser Controller
- **Operations on Campaigns** — Campaign Controller
- **Operations on Sponsorships** — Sponsorship Controller
- **Operations on Channels** — Channel Controller

## Why Jentic

- **Setup:** Wiring the Adshot Core service by hand means reading its spec, building calls across its gamers and advertisers endpoints, and handling request formatting and retries yourself. Through Jentic you install once, import Adshot Core from the API Directory, store any required connection detail once, and your agent calls it.
- **Permission scoping:** Adshot Core puts the gamer and advertiser ids in the URL path (`/v1/gamers/{id}`, `/v1/advertisers/{id}`), so a rule can pin your agent to reading one gamer or one advertiser. You choose the operations it may call, so the PATCH update operations are not included unless you add them.
- **Credential handling:** Any connection detail the Adshot Core service needs is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list or search all gamers', and Jentic returns the matching Adshot Core operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the API of the Adshot Core service
 use?

The API of the Adshot Core service
 uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I list / search all gamers. with the API of the Adshot Core service
?

Yes. Use the GET `/v1/gamers` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the API of the Adshot Core service
?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I list / search all gamers. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list / search all gamers.'. Jentic returns the matching API of the Adshot Core service
 operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the API of the Adshot Core service
 have?

The API of the Adshot Core service
 exposes 34 endpoints covering operations on gamers, operations on advertisers, operations on campaigns operations.

### Can I limit what my agent is allowed to do with the Adshot Core API?

Yes. Because you run Jentic One yourself, your own rules decide which Adshot Core operations and credentials your agent can use. Adshot Core puts the gamer and advertiser ids in the URL path (`/v1/gamers/{id}` and `/v1/advertisers/{id}`), so a rule can pin your agent to reading a single gamer or advertiser. You choose the operations it may call, so the PATCH update operations stay excluded unless you add them.