Scavio

🚀 Quickstart

Connect to Scavio with Nango and see data flow in 2 minutes.

Create the integration

In Nango (free signup), go to Integrations -> Configure New Integration -> Scavio.

Authorize Scavio

Go to Connections -> Add Test Connection -> Authorize, then enter your API Key. Later, you’ll let your users do the same directly from your app.

Call the Scavio API

Let’s make your first request to the Scavio API (a Google search). Replace the placeholders below with your Environment API key, integration ID, and connection ID:

cURL
Node

curl -X POST "https://api.nango.dev/proxy/api/v2/google" \
  -H "Authorization: Bearer <NANGO-API-KEY>" \
  -H "Provider-Config-Key: <INTEGRATION-ID>" \
  -H "Connection-Id: <CONNECTION-ID>" \
  -H "Content-Type: application/json" \
  -d '{"query": "coffee grinders"}'

Install Nango’s backend SDK with npm i @nangohq/node. Then run:

import { Nango } from '@nangohq/node';

const nango = new Nango({ apiKey: '<NANGO-API-KEY>' });

const res = await nango.post({
    endpoint: '/api/v2/google',
    providerConfigKey: '<INTEGRATION-ID>',
    connectionId: '<CONNECTION-ID>',
    data: { query: 'coffee grinders' }
});

console.log(res.data);

Or fetch credentials with the Node SDK or API.✅ You’re connected! Check the Logs tab in Nango to inspect requests.

Implement Nango in your app

Follow our quickstart to integrate Nango in your app.To obtain your own credentials, follow the setup guide linked below.

API gotchas

Scavio is billed in credits, not requests. Most endpoints cost 1 credit per call, but some cost more, so read the per-endpoint cost in the docs before running a large sync.

Platform endpoints live under two versions. Google search endpoints are on /api/v2/google; the other platforms are on /api/v1/<platform>/.... Copy the path from the endpoint’s docs page rather than deriving it, since a few paths do not match their platform name.

The generic extract endpoint is POST /api/v1/extract, which is not tied to a platform. It takes a URL and returns Markdown, plain text or HTML, and is priced by tier rather than by the flat per-call cost most platform endpoints use.

Most endpoints are POST with a JSON body. Calling one with GET returns a 404 rather than a 405, which reads like a missing endpoint.

Overview

1,000+ APIs & Integrations

🚀 Quickstart

📚 Scavio integration guides

API gotchas

🧩 Pre-built syncs & actions for Scavio

​🚀 Quickstart

​📚 Scavio integration guides

​API gotchas

​🧩 Pre-built syncs & actions for Scavio

🚀 Quickstart

📚 Scavio integration guides

API gotchas

🧩 Pre-built syncs & actions for Scavio