> Reverse Contact API documentation. This is the Markdown copy of https://docs.reversecontact.com/sdk/javascript/without-the-sdk
> Every page is listed at https://docs.reversecontact.com/llms.txt, every endpoint with its credit cost and status at https://docs.reversecontact.com/catalog.json

# Without the SDK

> Call the Reverse Contact API from any HTTP client, authenticate with a Bearer token, and use the OpenAPI specification to generate a typed client.

- Last verified: 2026-11-04

Call Reverse Contact with the HTTP client that fits your application.

## Use an HTTP client

The API accepts JSON over HTTPS, so you can use any HTTP client. Send your key in an `Authorization: Bearer` header, as shown in the cURL examples on each endpoint page.

To generate your own typed client, use the [published OpenAPI specification](https://docs.reversecontact.com/openapi.json). Follow [Error handling & retries](https://docs.reversecontact.com/guides/errors-retries) and [Polling](https://docs.reversecontact.com/guides/polling) to add the behavior the SDK handles for you.

## Find request examples

Start with [Your first API call](https://docs.reversecontact.com/guides/first-api-call) or choose an endpoint in the [API reference](https://docs.reversecontact.com/api-reference). Each endpoint documents its request, response and credit cost. The [Python SDK overview](https://docs.reversecontact.com/sdk/python) covers the other official SDK.

For the TypeScript client, see [Install and configure](https://docs.reversecontact.com/sdk/javascript/install).

Return to the [TypeScript SDK overview](https://docs.reversecontact.com/sdk/javascript).

## FAQ

### Can I use the Reverse Contact API without an SDK?

The Reverse Contact API accepts JSON over HTTPS from any HTTP client. Authenticate with an `Authorization: Bearer` header.

### Where is the Reverse Contact OpenAPI specification?

Use the OpenAPI specification at `https://docs.reversecontact.com/openapi.json` to generate a typed client.

### What must a custom API client handle?

A custom client handles authentication, HTTP errors and retry rules, and polls asynchronous jobs when needed. The Error handling & retries and Polling guides describe those behaviors.