Figure Eight Job Ontology API

openapi: 3.0.0
info:
  title: Appen Platform Account Info Job Ontology API
  version: 1.0.0
  description: "# Introduction\nHello, and welcome to Appen, the leading data annotation platform for Machine Learning. Our API enables developers to build applications that can programmatically create, edit, and launch Appen jobs, download results, and more! \n\nAppen uses a RESTful API that accepts data requests as URL-encoded key-value pairs. Responses are returned in JSON and authentication is key-based.\n\nBefore integrating with the API, we highly recommend you first build and run a job using our [graphical user interface](https://client.appen.com/sessions/new). Once you have run a job successfully and are satisfied with the results, you can automate the process using the Appen API.\n\n# Authentication\nYou will need to supply your Appen API key to access the API. To find your API key:\n1. Click the Account button located in the bottom corner of the Global Navigation bar on the left side of any page.\n![Appen Authentication](/assets/img/authentication1.png \"Appen Authentication\")\n2. Click the API tab and find your key listed under the Your API Key section. \n![Appen API](/assets/img/authentication2.png \"Appen API key\")\n\nFor requests listed below, the API Key will be listed as `{api_key}`. \n\nThe API key needs to be included in the header for every request: \n```\n  headers: { \n\n   \"AUTHORIZATION\" => \"Token token={api_key}\" \n\n  } \n```\n\nYou may also see other variables, such as `{job_id}` for operations pertaining to a specific job, or `{team_id}` when completing operations relevant to an entire team (like listing all available jobs). Job ID's can be determined from the job listing page or the URL. A team id is visible in the URL of the Teams tab in the Account page. \n# Resources\nThere are three primary data objects on Appen that correspond to resources on the API:\n## Jobs\nA **Job** is an interface that connects your data to an online workforce.\n  Each job on the Appen platform has data, instructions, customizable questions for your use case\n  (written in **CML** [](https://success.appen.com/hc/en-us/articles/202817989-CML-Custom-Markup-Language-Overview)),\n  [test questions](https://success.appen.com/hc/en-us/articles/202702985-How-to-Create-Test-Questions),\n  and is worked on by *Contributors*. Contributors submit *Judgments* on the rows of data via a worker interface. \n    * All jobs in a single account can be found [on your jobs page](https://client.appen.com/jobs) and will be\n    identified by a unique numeric id.\n## Units (also known as 'Rows')\nA **Unit** of data is uploaded to the job from your source data file via API or GUI. \n## Judgments \nA **Judgment** is the set of responses submitted by a contributor on a particular unit of data. It is\n  recommended to collect multiple judgments and compare them to one another or aggregate to the top response. For\n  each job, you can specify the number of judgments you would like each row to receive.\n# Responses and Messaging\nEach request to the Appen API returns an HTTP status code response and one or both of the following:\n* An application response message (in JSON) \n* A JSON representation of the object (job, unit, or judgments) requested\nSee the below sections of different API Requests, Responses and Messaging for more information:\n1. [Job Create/Update](/#tag/Job-CreateUpdate)\n2. [Manage Job Data](/#tag/Manage-Job-Data)\n3. [Job Status](/#tag/Job-Status)\n4. [Monitor Contributors](/#tag/Monitor-Contributors)\n5. [Manage Job Settings](/#tag/Manage-Job-Settings)\n6. [Job Results](/#tag/Job-Results)\n7. [Account Info](/#tag/Account-Info)\n"
  license:
    name: Licensed under Apache 2.0
    url: http://www.apache.org/licenses/LICENSE-2.0.html
  termsOfService: https://www.appen.com/privacy-statement/
  contact:
    email: help@appen.com
servers:
- url: https://api.appen.com/v1
  description: Production Server
tags:
- name: Job Ontology
  description: Read and Update the Ontology for a job
  externalDocs:
    url: https://success.appen.com/hc/en-us/articles/360015150252-Guide-To-Ontology-Manager
paths:
  /jobs/{job_id}/ontology:
    get:
      servers:
      - url: https://api-proxy.appen.com/v1
        description: Production Server
      tags:
      - Job Ontology
      summary: Get Job Ontology
      description: Get the Ontology from a Job in JSON format.
      parameters:
      - $ref: '#/components/parameters/job_id'
      - $ref: '#/components/parameters/api_key'
      responses:
        '200':
          description: JSON Array describing the Ontology
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ontology'
      x-code-samples:
      - lang: Shell
        label: cURL
        source: 'curl -X GET \

          "https://api-proxy.appen.com/v1/jobs/{job_id}/ontology"

          -H "Authorization: Token token={api_key}"

          '
    put:
      servers:
      - url: https://api-proxy.appen.com/v1
        description: Production Server
      tags:
      - Job Ontology
      summary: Update Job Ontology
      description: 'Update the Ontology for a Job. If the Ontology doesn''t exist then a new Ontology

        is created. (Note: Not all Job types accept a JSON formatted Ontology, please

        refer to the [documentation](https://success.appen.com/hc/en-us/articles/360015150252-Guide-To-Ontology-Manager?mobile_site=false)

        for more information).

        '
      parameters:
      - $ref: '#/components/parameters/job_id'
      - $ref: '#/components/parameters/api_key'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ontology'
      responses:
        '200':
          description: OK - The Ontology was updated.
      x-code-samples:
      - lang: Shell
        label: cURL
        source: "curl -X PUT \\\n\"https://api-proxy.appen.com/v1/jobs/{job_id}/ontology\"\\\n-H \"Authorization: Token token={api_key}\" \\\n--data-raw '[\n  {\n    \"description\": \"Ego vehicle, parking, static objects (trash bins), dynamic (garbage on sidewalk), bridge... etc. (see job description if unsure)\",\n    \"class_name\": \"void\",\n    \"display_color\": \"#000000\",\n    \"children\": [\n            {\n                \"description\": \"Children of the void class\",\n                \"class_name\": \"children\",\n                \"display_color\": \"#ca03fc\"\n            }\n        ]\n  }\n]'\n"
  /jobs/{job_id}/ontology.csv:
    get:
      servers:
      - url: https://api-proxy.appen.com/v1
        description: Production Server
      tags:
      - Job Ontology
      summary: Get Job Ontology (CSV)
      description: Get the Ontology from a Job in CSV format.
      parameters:
      - $ref: '#/components/parameters/job_id'
      - $ref: '#/components/parameters/api_key'
      responses:
        '200':
          description: The Ontology data formated in CSV.
          content:
            text/plain:
              schema:
                type: string
                example: 'description,class_name,display_color,

                  "NOT Ego vehicle, parking, static objects (trash bins), dynamic (garbage on sidewalk), bridge... etc. (see job description if unsure)",not_void,#000000

                  '
      x-code-samples:
      - lang: Shell
        label: cURL
        source: 'curl -X GET \

          "https://api-proxy.appen.com/v1/jobs/{job_id}/ontology.csv"

          -H "Authorization: Token token={api_key}"

          '
    put:
      servers:
      - url: https://api-proxy.appen.com/v1
        description: Production Server
      tags:
      - Job Ontology
      summary: Update Job Ontology (CSV)
      description: 'Update the Ontology for a Job. If the Ontology doesn''t exist then a new Ontology

        is created. (Note: Not all Job types accept a CSV formatted Ontology, please

        refer to the [documentation](https://success.appen.com/hc/en-us/articles/360015150252-Guide-To-Ontology-Manager?mobile_site=false)

        for more information).

        '
      parameters:
      - $ref: '#/components/parameters/job_id'
      - $ref: '#/components/parameters/api_key'
      requestBody:
        description: 'A **CSV** formatted file of the Ontology to upload to the Job.

          '
        content:
          multipart/form-data:
            schema:
              type: string
              format: binary
      responses:
        '200':
          description: OK - The Ontology was updated.
      x-code-samples:
      - lang: Shell
        label: cURL
        source: 'curl -X PUT \

          "https://api-proxy.appen.com/v1/jobs/{job_id}/ontology"\

          -H "Authorization: Token token={api_key}" \

          --form ''file=@{path_to_csv}''

          '
components:
  schemas:
    ontology:
      description: A JSON array representing the Ontology.
      type: array
      items:
        type: object
        properties:
          class_name:
            type: string
          display_color:
            description: Must be a hex color string e.g. (#F42069)
            type: string
          description:
            type: string
        required:
        - class_name
    new_job_id:
      description: Integer identifier of the requested resource (Job, Unit, Workflow) used in API request paths and response bodies.
      type: integer
      format: int64
      readOnly: true
      minimum: 1
      maximum: 9223372036854776000
      example: 1234567
  parameters:
    api_key:
      name: key
      in: query
      required: true
      description: "Your personal Appen API key; used to access the Appen platform. Can be found in your [account settings](https://client.appen.com/account/api). Variable name: `{api_key}`. \n"
      schema:
        type: string
    job_id:
      in: path
      name: job_id
      description: "A unique identifier for a job or task that is distributed to contributors. Variable name: `{job_id}`. \n"
      required: true
      schema:
        $ref: '#/components/schemas/new_job_id'