Skip to main content
Reconify publishes one canonical OpenAPI artifact, so Postman can work from the same contract this reference documents. No separately maintained collection exists, which means nothing drifts from the generated spec.

​
Import the contract

Three steps take you from the spec URL to a validated key.
1

Import the OpenAPI URL

In Postman, Import takes a Link:
The option that creates a collection from the specification produces a collection holding only the public /v2 operations.
2

Set collection authorization

The collection’s authorization settings take Bearer Token. A Postman variable holds the key, which keeps it out of individual requests:
The token value then reads {{reconify_api_key}}, marked secret wherever your workspace supports that control.
A real key never syncs into a workspace with broader membership than the Reconify organization, and an environment containing it never gets exported or committed.
3

Validate the key

GET /v2/events with limit=1 is the test, because GET /v2 and GET /v2/health answer without checking credentials.
  • 200 confirms the key reads data in its organization.
  • 401 means the key is missing or invalid.
  • 403 means the key is valid but lacks the required access.

​
Before you run a write request

Reconify has no sandbox or test mode, and POST /v2/events writes immutable evidence to the organization behind the key. Send events covers what a safe first request looks like. When the public contract changes, a re-import of the canonical artifact picks it up. The versioned manifest carries checksums and version locations for automated consumers.