Skip to main content

Keys and access

Do I need separate read and write keys?

Separate keys are the recommended shape. A sender holds a write key, a reader holds a read key, and an admin key covers a service that genuinely does both.

Can API keys read issues?

Yes. A read or admin key reaches events, issues, evidence, notes, and organization data.

Why did I receive 401 or 403?

401 means the key is missing or invalid. 403 means the key is valid but its scope does not cover the method.

What data can the API return?

The API returns monitoring events, finding messages, evidence, notes, organization data, and member IDs and roles. Member email addresses stay out of every response. Everything it does return counts as customer data.

Sending events

What does 202 Accepted mean?

Reconify stored at least one event in the batch, or found a duplicate. It says nothing about whether the operation passed evaluation.

How does event.id work in a batch?

It identifies one event inside your organization. A retry with the same ID and payload returns duplicate, and the same ID with different content returns idempotency_conflict.

What happens when an event is duplicated?

The item result reads duplicate, which counts as delivered.

What happens when a note request is retried?

An optional Idempotency-Key header covers it. The same key with the same request replays the original note, and the same key with another issue or body returns 409 idempotency_conflict.

Reading and investigating

Why is a finding resolved late?

The required evidence arrived after the deadline. Reconify preserves the timing and marks the finding resolved_late.

How do cursors work?

The next_cursor value from one list response becomes the after parameter of the next request. The cursor is opaque, so it passes through untouched.

Where is service status?

GET /v2/health carries the public health signal, and the status page carries service updates.