canonical: https://jentic.com/apis/stitchdata.com/stitchdata

# Stitch Data API

Stitch Data ETL platform API for managing sources, destinations, streams, replication jobs, and data import. The API exposes 33 endpoints.

## For AI agents

Programmatically get import API status, push data batch to stitch. Covers 33 operations.

## Scope

Does not handle payments, communications, or crm - use for hr and recruiting only.

## Capabilities

- Get Import API status
- Push data batch to Stitch
- Validate a push request
- Create a new Stitch account
- Generate ephemeral session token
- List all destination types

## Use cases

### HR and Recruiting Operations

Use the Stitch Data API to perform hr recruiting operations programmatically. The API provides 33 endpoints covering core functionality including get import API status, push data batch to stitch, validate a push request.

Example prompt: Call GET /v2/import/status to get import API status

### Automated Accounts Management

Automate accounts operations by combining multiple Stitch Data API endpoints. Agents can push data batch to stitch and then validate a push request in a single workflow.

Example prompt: Call POST /v2/import/batch to push data batch to stitch, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Stitch Data API 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 'get import API status', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /v2/import/status | Get Import API status |
| POST | /v2/import/batch | Push data batch to Stitch |
| POST | /v2/import/validate | Validate a push request |
| POST | /v2/import/push | Push data for one or multiple tables |
| POST | /v3/accounts | Create a new Stitch account |
| POST | /v3/sessions/ephemeral | Generate ephemeral session token |
| GET | /v4/destination-types | List all destination types |
| GET | /v4/destination-types/{destination_type} | Get destination type info |

## Key resources

- **Accounts** — Operations related to Accounts
- **Destination Types** — Operations related to Destination Types
- **Destinations** — Operations related to Destinations
- **Import API** — Operations related to Import API
- **Notifications** — Operations related to Notifications

## Why Jentic

- **Setup:** Wiring the Stitch Data API by hand means obtaining a bearer token, sending it on every call to api.stitchdata.com, and keeping track of its mixed v2, v3, and v4 endpoint versions yourself. Through Jentic you install once, import the Stitch Data API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Stitch puts the source id in the URL path (/v4/sources/{source_id}/...), so a rule can pin your agent to one source: reading its streams and metadata and nothing else. You choose the operations it may call, so triggering a sync or deleting a source is not included unless you add it.
- **Credential handling:** Your Stitch Data API token 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 'check import status' or 'list a source's streams', and Jentic returns the matching Stitch Data API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Greenhouse** — Alternative hr recruiting API
- **Lever** — Alternative hr recruiting API
- **Workday** — Complementary hr recruiting API

## FAQ

### What authentication does the Stitch Data API use?

The Stitch Data API 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 get import API status with the Stitch Data API?

Yes. Use the GET /v2/import/status endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Stitch Data API?

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 get import API status through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get import API status'. Jentic returns the matching Stitch Data API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Stitch Data API have?

The Stitch Data API exposes 33 endpoints covering accounts, destination types, destinations operations.

### Can I limit what my agent is allowed to do with the Stitch Data API?

Yes. Because you run Jentic One yourself, your own rules decide which Stitch Data API operations and credentials the agent may use. Since Stitch puts the source id in the URL path, such as /v4/sources/{source_id}/, you can pin the agent to a single source and let it only read that source's streams and metadata. You choose the operations it may call, so actions like triggering a sync via /v2/import/batch or deleting a source stay off limits unless you explicitly add them.