import.io Schedule API

Name: import.io Schedule API
Brand: import.io Schedule API
Availability: InStock

✓ Official Vendor SpecData EnrichmentData TransformationapiKey4 EndpointsREST

Install Jentic One Beta

Connect the import.io Schedule API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the import.io Schedule API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fimport.io%2Fimport-io-schedule" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fimport.io%2Fimport-io-schedule" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with import.io Schedule API.

List schedules across all extractors in an account

Schedule an extractor to run at a specific time or cadence

Retrieve the schedule for one extractor

Delete an existing schedule from an extractor

GET STARTED

Start building with import.io Schedule API

Explore with Jentic One

View OpenAPI Document

For Agents

Manage recurring crawl schedules for import.io extractors. Useful for automating periodic data collection without manual run triggers.

Use for: I want to schedule an extractor to run daily, List all current extractor schedules on my account, Get the schedule attached to a specific extractor, Delete the schedule on an extractor

Not supported: Does not run crawls inline, return result rows, or build extractors - use for managing recurring extractor schedules only.

Use Cases

Patterns agents use import.io Schedule API for, with concrete tasks.

★ Recurring Data Collection

Set up regular scrape cadences for extractors that feed dashboards, alerting, or BI. Use POST /extractor to schedule an extractor at a specific time and GET /extractor to confirm the schedule is in place. The schedule then triggers crawl runs without manual intervention.

Schedule extractor ext-prices to run every day at 06:00 UTC and confirm the schedule shows up in GET /extractor.

Schedule Audit Across Account

Operations teams can list every active schedule on the account using GET /extractor. The list view makes it straightforward to see which extractors are scheduled, when they run, and which extractors are still on manual triggering.

List all extractor schedules and report any extractor missing a schedule from the expected list.

Schedule Cleanup

Decommissioning an extractor or moving to on-demand triggering means deleting the existing schedule. DELETE /extractor/{extractorId}/ removes the schedule cleanly so the extractor only runs when explicitly invoked through the Run API.

Delete the schedule on extractor ext-old-feed and confirm the schedule no longer appears in GET /extractor.

Jentic-Driven Schedule Manager

Through Jentic, an agent can manage extractor schedules from a chat surface. The agent searches for a schedule operation, loads the schema, and creates, retrieves, or deletes schedules without learning the endpoint paths.

Search Jentic for 'schedule an extractor to run', load the schema, and create a daily 09:00 UTC schedule for extractor ext-jobs.

Key Endpoints

4 endpoints — the import.

METHOD

PATH

DESCRIPTION

GET

/extractor

List schedules for all extractors

POST

/extractor

Schedule an extractor to run at a specific time

GET

/extractor/{extractorId}/

Get the schedule for one extractor

DELETE

/extractor/{extractorId}/

Delete an existing schedule

GET

/extractor

List schedules for all extractors

POST

/extractor

Schedule an extractor to run at a specific time

GET

/extractor/{extractorId}/

Get the schedule for one extractor

DELETE

/extractor/{extractorId}/

Delete an existing schedule

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the import.io Schedule API by hand means passing your apikey as a query parameter and pointing at the dedicated schedule.import.io host, distinct from the run and rss hosts. Through Jentic you install once, import the import.io Schedule API from the API Directory, store the apikey once, and your agent calls it.

Permission scoping

The Schedule API puts the extractor id in the URL path (/extractor/{extractorId}/), so a rule can pin your agent to reading a schedule for one extractor. You choose the operations it may call, so creating or deleting schedules is not included unless you add it.

Credential isolation

Your import.io apikey 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.

Intent-based discovery

Agents search Jentic by intent such as 'schedule an extractor' or 'list extractor schedules', and Jentic returns the matching import.io Schedule operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using import.io Schedule API through Jentic.

What authentication does the import.io Schedule API use?

The Schedule API uses an apikey query parameter on every request. Through Jentic, the apikey is stored in the encrypted vault and injected at runtime, so the raw key never enters agent prompts.

Can I list all schedules on my account?

Yes. GET /extractor returns the list of schedules for every extractor on the account, which is useful for auditing scrape cadence and spotting extractors that are still on manual triggering.

What are the rate limits for the import.io Schedule API?

The published spec does not declare explicit rate limit numbers. Schedule operations are infrequent by nature, so most agents stay well below import.io's per-account quotas regardless of plan tier.

How do I create a daily schedule for an extractor through Jentic?

Search Jentic for 'schedule an extractor to run' to find the operation backed by POST /extractor. Load the schema, pass the extractor id and desired time, and execute. Jentic injects the apikey at runtime.

How do I remove a schedule from an extractor?

Call DELETE /extractor/{extractorId}/ with the extractor id. The response confirms removal. The extractor will then only run when triggered manually via the Run API or rescheduled.

Can I limit what my agent is allowed to do with the import.io Schedule API?

Yes. Because you run Jentic One yourself, your own rules decide which of the Schedule API's operations your agent may call and which credentials it may use. You can allow only reading a schedule with GET /extractor/{extractorId}/ for a single extractor id in the path, while withholding POST /extractor and DELETE /extractor/{extractorId}/ so the agent cannot create or delete schedules unless you grant it. The apikey stays with your instance and is applied at run time, never exposed to the agent.

import.io Schedule API

Connect the import.io Schedule API to your agent

Capabilities

Start building with import.io Schedule API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs