# Zapier

> [!warning] No Zapier app at launch
> There is no published SciSpace Zapier app. Until there is, use Zapier's **Webhooks by Zapier**
> action to call the API directly — everything below works today with no integration to wait for.

## Calling the API from a Zap

Use a **Custom Request** action:

| Field | Value |
|---|---|
| Method | `POST` |
| URL | `https://api.scispace.com/v1/searches` |
| Headers | `Authorization: Bearer sk_live_…`, `Content-Type: application/json` |
| Data | `{"query": "{{query_from_previous_step}}", "depth": "standard"}` |

> [!danger] Zapier stores your key
> Anyone with access to the Zap can read the header. Use a dedicated key with the minimum scopes and a
> per-key monthly credit cap (api-keys).

## Handling async

Searches return `202` with `status: queued`, so a single Zap step will not have the answer. Two
options:

1. **Webhook (recommended).** Register a webhook endpoint pointing at a *Catch Hook* trigger in a second Zap, subscribed to `search.completed`. The event carries the full resource — no follow-up call needed.
2. **Delay then fetch.** *Delay For* 30 seconds, then `GET /v1/searches/{id}`. Simpler, but fragile at `deep_review` depth where p95 is 240 seconds.

## What a first-party app would expose

If you would use one, tell us at `api-feedback@scispace.com` — the shortlist is: action *Run a
literature search*, action *Extract fields from a PDF*, trigger *Search completed*.

## Related

webhook-endpoints · searches · api-keys