canonical: https://jentic.com/apis/swaggerhub.jensmostaert3/api-of-the-adshot-scraping-engine # Jensmostaert3 API of the Adshot Scraping Engine This is the API definition for the Adshot Scraping Engine service. This API should only be made available internally for use by Adshot Core. There is no dependency in the other direction. Meaning that the Scraping Engine API should not fetch data from Adshot Core or store foreign keys to entities stored in Adshot Core, thereby avoiding coupling between these services as much as possible. Mappings . The API exposes 14 endpoints. ## For AI agents Programmatically create a new channel job., list / search all channel scrape jobs.. Covers 14 operations. ## Scope Does not handle payments, communications, or crm - use for maps and geolocation only. ## Capabilities - Create a new Channel Job. - List / search all Channel scrape jobs. - Retrieve details of a specific Channel Job. - Update a Channel Job. - Delete a specific Channel Job. ## Use cases ### Maps and Geolocation Operations Use the API of the Adshot Scraping Engine to perform maps geolocation operations programmatically. The API provides 14 endpoints covering core functionality including create a new channel job., list / search all channel scrape jobs., retrieve details of a specific channel job.. Example prompt: Call POST /v1/channels/jobs to create a new channel job. ### Automated Operations on Channels Management Automate operations on channels operations by combining multiple API of the Adshot Scraping Engine endpoints. Agents can list / search all channel scrape jobs. and then retrieve details of a specific channel job. in a single workflow. Example prompt: Call GET /v1/channels/jobs to list / search all channel scrape jobs., then verify the result ### AI Agent Integration via Jentic AI agents discover and call API of the Adshot Scraping Engine 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 'create a new channel job.', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /v1/channels/jobs | Create a new Channel Job. | | GET | /v1/channels/jobs | List / search all Channel scrape jobs. | | GET | /v1/channels/jobs/{id} | Retrieve details of a specific Channel Job. | | PATCH | /v1/channels/jobs/{id} | Update a Channel Job. | | DELETE | /v1/channels/jobs/{id} | Delete a specific Channel Job. | | GET | /v1/channels/scrapes | List / search all Channel scrapes. | | GET | /v1/channels/scrapes/{id} | Retrieve details of a specific Channel Scrape. | | POST | /v1/media/jobs | Create a new Media Job. | ## Key resources - **Operations on Channels** — Jobs Controller - **Operations on Media** — Media Controller ## Why Jentic - **Setup:** Wiring the Adshot Scraping Engine by hand means reading its spec, building calls across its channel jobs, scrapes, and media jobs endpoints, and handling request formatting and retries yourself. Through Jentic you install once, import the Adshot Scraping Engine from the API Directory, store any required connection detail once, and your agent calls it. - **Permission scoping:** The Scraping Engine puts the job and scrape ids in the URL path (/v1/channels/jobs/{id}, /v1/channels/scrapes/{id}), so a rule can pin your agent to reading one channel job or scrape. You choose the operations it may call, so the PATCH update and DELETE on a job are not included unless you add them. - **Credential handling:** Any connection detail the Adshot Scraping Engine 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 'create a new channel scraping job', and Jentic returns the matching Adshot Scraping Engine operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Here** — Alternative maps geolocation API - **Tomtom** — Alternative maps geolocation API - **Googleapis** — Complementary maps geolocation API ## FAQ ### What authentication does the API of the Adshot Scraping Engine use? The API of the Adshot Scraping Engine 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 create a new channel job. with the API of the Adshot Scraping Engine ? Yes. Use the POST /v1/channels/jobs 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 Scraping Engine ? 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 create a new channel job. through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a new channel job.'. Jentic returns the matching API of the Adshot Scraping Engine 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 Scraping Engine have? The API of the Adshot Scraping Engine exposes 14 endpoints covering operations on channels, operations on media operations. ### Can I limit what my agent is allowed to do with the Adshot Scraping Engine API? Yes. Jentic One is self-hosted by you, so your own rules decide which Adshot Scraping Engine operations and connection details the agent may use. Because the API carries each job and scrape id in the URL path (/v1/channels/jobs/{id} and /v1/channels/scrapes/{id}), you can pin the agent to reading a single channel job or scrape. You choose the operations it may call, so the PATCH update and DELETE on a job stay out of reach unless you explicitly grant them.