Configure the API intake source

You can set up external APIs that send documents to Oracle Safety One Argus to be reviewed in the Intake Worklist. In this configuration step, you need to define a source name in the INTAKE_SOURCE code list for external APIs and how the documents coming from the API will be handled.

  1. Log in to Oracle Safety One Argus and click Argus Console.
  2. From the Code Lists context menu, click Flexible Data Re-categorization.
  3. Select Flexible Data Re-categorization from the node tree panel.
  4. In the Code List Name drop down menu, select INTAKE_SOURCE.
  5. Use the table below to provide valid values during the configuration.

    Table 3-2 INTAKE_SOURCE configuration

    Attribute Valid Values Description Notes
    Source_Type 0, 1

    0 = Source is Manual Upload

    1 = Source is API

    		 For API sources, the Source_Type must always be 1.
    Source_Name Varchar The Source_Name specified here is displayed with ingested records in the Intake Worklist's Source column. We recommend using the API Contract Name as the Source_Name.
    Triage_Required 0, 1

    0 = Trusted Source

    1 = Untrusted Source
    • This attribute only applies to Source_Type = 1.
    • If Triage_Required = 0, then the ingested record from the corresponding API Source skips the manual Check Validity task.
    • If Triage_Required = 1, then the ingested record from the corresponding API Source is always flagged for manual Check Validity and appears in the Intake Worklist.
    • If the incoming API request contains Triage_Required value, then it takes precedence over the Triage_Required value configured at source.
    Multi-Case 0, 1

    0 = All documents are treated as one case

    1 = Each document is treated as a single case
    • This attribute is applicable only when there are multiple documents in one record.
    • If Multi-Case = 0, then the multiple documents in the ingested record are treated as a single case.
    • If Multi-Case = 1, then each document in the ingested record is treated as a single case, resulting in multiple potential cases.
    • If the incoming API request contains Multi-Case flags, then it overwrites the Multi-Case state configured at source.
    • This attribute is only applicable when Source_Type = 1.

Parent topic: Argus Console configurations