Ingest API Overview

The Ours Privacy Ingest API sends events, identifies visitors, and tracks conversions directly from your backend. Use it when data originates on your servers rather than a user's browser — form submissions, server-side conversions, CRM syncs, or offline activity.

The API is available at https://api.oursprivacy.com/api/v1/ and follows standard REST conventions. Each request is authenticated with a source API key sent in the request body.

---

Why Use the Ingest API?

• Capture backend and offline events — track activity that never touches a browser, like CRM status changes or in-person purchases
• Stay complete when scripts are blocked — collect events even when a visitor has disabled JavaScript or blocked the tracking script
• Send sensitive data securely — submit events directly from a secure server environment instead of the client
• Backfill history — import past events with their original timestamps

---

Endpoints

---

SDKs

If you'd rather not call the REST API directly, see SDKs — wrappers for Node.js, Python, Go, Ruby, PHP, C#, and Kotlin. All send to the same Ingest API and are described by the same OpenAPI specification.

---

Key Concepts

• Base URL: https://api.oursprivacy.com/api/v1/
• Authentication: a source API key (token) sent in the request body (see Authentication)
• Visitor identification: include at least one of userId, externalId, or email to associate data with a visitor
• OpenAPI spec: available at GET /api/v1/openapi
• Test Mode: a separate key stores events for review without dispatching them to destinations

---

Getting Started

1. Add an Ingest API source and set up authentication: create the source that issues your API key.
2. Make your first request: send a Purchase event with a single curl command.

---

Need Help?

If you have questions about the Ingest API or need assistance, reach out to support@oursprivacy.com.