Get organization context

This page documents the canonical HTTP contract. Switch to the CLI example when you want the operator workflow.

Use a signed-in user session. Developer API keys are blocked for this route. Records are scoped to the current organization.

Case-study reads project terminal ingestion status from the canonical operation receipt, so processing_status can show completed, failed, or cancelled even if a worker stopped before updating the asset record. Pending assets can show queued or processing; failures can include processing_error. The internal ingestion checkpoint is omitted. Read operation-run progress with operation_run_id; job_id is a separate native identity. Examples are abridged.

Errors

Status	Meaning
401	A signed-in user session and organization context are required.
403	Developer API keys are blocked, or the caller lacks administrator permission for a write.
404	User or organization not found.
422	Invalid request fields.
500	Context read, save, or case-study admission failed.

Example

bash

curl "https://app.autotouch.ai/api/org/context" -H "Authorization: Bearer $USER_SESSION_TOKEN"

Response example

json

{
  "organization_id": "org_example",
  "seller": {},
  "default_icp": {},
  "fit_scoring": {},
  "setup": {},
  "case_studies": [
    {
      "case_study_id": "case_study_example",
      "type": "url",
      "url": "https://example.com/case-study",
      "processing_status": "queued",
      "job_id": "case-study-ingest-example",
      "operation_run_id": "oprun_case_study_example"
    }
  ],
  "enable_case_studies": true,
  "case_study_count": 1
}