Skip to main content
API docs by Redocly

Onna Platform API (v1.1.0)

Download OpenAPI specification:Download

URL: https://dev.onna.com/help License: Apache 2.0 Terms of Service

Introduction

Onna

The Onna Platform API enables you to programmatically upload your data into our Knowledge Integration Platform. This unlocks the possibility to have all your data in one place and turn it into knowledge—even data we don't support directly with one of our connectors.

Key concepts

Before starting to use the API, we recommend to become familiar with some key concepts. For more information on the key concepts, see API basics.

Requirements

To use this API, you must have an active account on an Enterprise Plan and have the Developer role assigned.

For more information, see Requirements.

Security

This API requires that all requests are made using HTTPS and must be authenticated with a valid token.

Response codes

A full list of the response codes returned by this API is available at Response codes.

Versioning

This API uses semantic versioning to ensure that your client doesn't break. The version is declared in the URL so that you can lock to a specific one by prefix the URL.

When the version declared in the URL is not supported, you will receive a 400 response.

For more information, see Versioning.

Date and time format

This API supports dates and times in ISO 8601 format.

Pagination

This API uses cursoring to divide large sets of results in multiple pages. For more information, see Pagination.

Parameters

There are many ways to pass parameters when making requests to this API. For more information, see Parameters.

Resource types

You can ingest various type of resources. For more information, see Resource types.

Authentication

Our API uses OAuth 2's Client Credentials Grant to authenticate your requests. This grant type is especially suited for machine-to-machine (M2M) applications, such as the applications you build on top of the Onna platform.

For more information please check our detailed authentication docs.

Login

Exchange credentials for an access token.

Authorizations:
OAuth2
Request Body schema: application/x-www-form-urlencoded
client_id
string (Client ID)

Unique client ID, generated in the Platform API app.

client_secret
string (Client Secret)

Unique client secret, generated in the Platform API app.

grant_type
string (Grant Type)
Default: "client_credentials"

Use the default value.

Responses

Request samples 

curl --request POST \
  --url 'https://api.onna.com/v1/oauth/token' \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data-urlencode 'client_id=YOUR_CLIENT_ID' \
  --data-urlencode 'client_secret=YOUR_CLIENT_SECRET' \
  --data-urlencode 'grant_type=client_credentials'

Response samples

Content type
application/json
{
  • "access_token": "<BEARER_TOKEN>",
  • "expires_in": 3599,
  • "token_type": "bearer"
}

Current User

Return information about the currently authenticated user.

Authorizations:
OAuth2
header Parameters
authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Responses

Response samples

Content type
application/json
{
  • "account_id": "foo",
  • "id": "test.user@onna.com",
  • "name": "Test",
  • "surname": "User"
}

Workspaces

Workspaces are locations where you can collect data coming from different sources, organize it, and collaborate with other members of your team.

You can share workspaces with collaborators with various permission levels and roles. Permission levels are dependent on the type of expected collaboration. You can also search across an entire workspace and export the results of your searches or entire data collections.

This collection includes all the endpoints that enable you to work and collaborate inside workspaces.

List Workspaces

List workspaces.

Authorizations:
OAuth2
query Parameters
cursor
string (Cursor)
Example: cursor=2022-02-22T11:11:11.12345
header Parameters
authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Responses

Request samples 

curl --location --request GET 'https://api.onna.com/v1/workspaces?cursor=100' \
--header 'Authorization: Bearer <ACCESS_TOKEN>' \
--header 'Accept: application/json'

Response samples

Content type
application/json
{
  • "cursor": "string",
  • "items": [
    ]
}

Create Workspace

Create a workspace.

Authorizations:
OAuth2
header Parameters
authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Request Body schema: application/json
description
string (Description)

Short description of the workspace.

name
required
string (Name)

Display name of the workspace.

tags
Array of strings (Tags) <= 10000 items

Labels attached to the workspace for the purpose of identification or to give meta information.

Responses

Request samples

Content type
application/json
{
  • "description": "My personal workspace",
  • "name": "My workspace",
  • "tags": [
    ]
}

Response samples

Content type
application/json
{
  • "onna_id": "ws6f0c5339de42f9964e6afe9bf20469"
}

Delete Workspace

Delete a Workspace.

Authorizations:
OAuth2
path Parameters
onna_id
required
string (Workspace ID)
Example: myworkspace-ZPM9Jf4zQ

Unique ID of the workspace.

header Parameters
authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Responses

Request samples 

curl --location --request DELETE 'https://api.onna.com/v1/workspaces/ws6f0c5339de42f9964e6afe9bf20469' \
--header 'Authorization: Bearer <ACCESS_TOKEN>' \
--header 'Accept: application/json'

Response samples

Content type
application/json
{
  • "errors": [
    ]
}

Retrieve Workspace Info

Retrieve information related to a workspace.

Authorizations:
OAuth2
path Parameters
onna_id
required
string (Workspace ID)
Example: myworkspace-ZPM9Jf4zQ

Unique ID of the workspace.

header Parameters
authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Responses

Request samples 

curl --location --request GET 'https://api.onna.com/v1/workspaces/ws6f0c5339de42f9964e6afe9bf20469' \
--header 'Authorization: Bearer <ACCESS_TOKEN>' \
--header 'Accept: application/json

Response samples

Content type
application/json
{
  • "description": "My personal workspace",
  • "name": "My workspace",
  • "onna_id": "ws6f0c5339de42f9964e6afe9bf20469",
  • "tags": [
    ]
}

Update Workspace

Update the workspace. For example, rename it from my-workspace to my-new-workspace.

Authorizations:
OAuth2
path Parameters
onna_id
required
string (Workspace ID)
Example: myworkspace-ZPM9Jf4zQ

Unique ID of the workspace.

header Parameters
authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Request Body schema: application/json
description
string (Description)

Short description of the workspace.

name
string (Name)

Display name of the workspace.

tags
Array of strings (Tags) <= 10000 items

Labels attached to the workspace for the purpose of identification or to give meta information.

Responses

Request samples

Content type
application/json
{
  • "description": "My personal workspace",
  • "name": "My workspace",
  • "tags": [
    ]
}

Response samples

Content type
application/json
{
  • "errors": [
    ]
}

List Workspace Custom Fields

List custom fields for a workspace.

Authorizations:
OAuth2
path Parameters
onna_id
required
string (Workspace ID)
Example: myworkspace-ZPM9Jf4zQ

Unique ID of the workspace.

query Parameters
cursor
string (Cursor)
Example: cursor=2022-02-22T11:11:11.12345
header Parameters
authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Responses

Request samples 

curl ...

Response samples

Content type
application/json
{
  • "cursor": "string",
  • "items": [
    ]
}

Enable Workspace Custom Field

Enable custom field for a workspace.

Authorizations:
OAuth2
path Parameters
onna_id
required
string (Workspace ID)
Example: myworkspace-ZPM9Jf4zQ

Unique ID of the workspace.

header Parameters
authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Request Body schema: application/json
onna_id
required
string (Onna ID)

Alphanumeric unique identifier of the workspace.

Responses

Request samples

Content type
application/json
{
  • "onna_id": "cf-b20696ae9"
}

Response samples

Content type
application/json
{
  • "errors": [
    ]
}

Read Workspace Custom Value

Get custom field value for a workspace.

Authorizations:
OAuth2
path Parameters
onna_id
required
string (Workspace ID)
Example: myworkspace-ZPM9Jf4zQ

Unique ID of the workspace.

field_id
required
string (Field ID)
Example: cf-b20696ae9

Unique ID of the field.

header Parameters
authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Responses

Request samples 

curl ...

Response samples

Content type
application/json
{
  • "onna_id": "cf-b20696ae9",
  • "value": "My custom field value"
}

Update Workspace Custom Value

Set custom field value for a workspace.

Authorizations:
OAuth2
path Parameters
onna_id
required
string (Workspace ID)
Example: myworkspace-ZPM9Jf4zQ

Unique ID of the workspace.

field_id
required
string (Field ID)
Example: cf-b20696ae9

Unique ID of the field.

header Parameters
authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Request Body schema: application/json
value
required
string (Value)

Custom field value

Responses

Request samples

Content type
application/json
{
  • "value": "My custom field value"
}

Response samples

Content type
application/json
{
  • "errors": [
    ]
}

Folders

Folders are containers for your files or other folders. A place where you can group your resources together, like in any desktop operating system.

This collection includes all the endpoints that enable you to handle folders, such as creating, retrieving, or deleting them.

Create Folder

Create a folder in a workspace.

Authorizations:
OAuth2
header Parameters
authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Request Body schema: application/json
name
required
string (Name)

Display name of the Folder.

onna_parent_id
required
string (Parent ID)

The ID of the parent Workspace or Folder.

Responses

Request samples

Content type
application/json
{
  • "name": "My folder",
  • "onna_parent_id": "b7c6f55fa54c4a3e821e825bd6262c0f"
}

Response samples

Content type
application/json
{
  • "onna_id": "8a8ead66ba6f4862b922a911dd67c439"
}

Delete Folder

Delete the folder. 📌 This also deletes all resources contained in it!

Authorizations:
OAuth2
path Parameters
onna_id
required
string (ID)

Unique ID of the folder.

header Parameters
authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Responses

Request samples 

curl --request DELETE \
--url 'https://api.onna.com/v1/folders/fd9f0c5339de42f9964e6afe9bf20259' \
--header 'Authorization: Bearer <ACCESS_TOKEN>' \
--header 'Accept: application/json'

Response samples

Content type
application/json
{
  • "errors": [
    ]
}

Retrieve Folder Info

Retrieve information related to a folder.

Authorizations:
OAuth2
path Parameters
onna_id
required
string (ID)

Unique ID of the folder.

header Parameters
authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Responses

Request samples 

curl --request GET \
--url 'https://api.onna.com/v1/folders/fd9f0c5339de42f9964e6afe9bf20259' \
--header 'Authorization: Bearer <ACCESS_TOKEN>' \
--header 'Accept: application/json' \

Response samples

Content type
application/json
{
  • "name": "My folder",
  • "onna_id": "fd9f0c5339de42f9964e6afe9bf20259"
}

Update Folder

Update the folder. For example, rename it from My folder to My updated folder name.

Authorizations:
OAuth2
path Parameters
onna_id
required
string (ID)

Unique ID of the folder.

header Parameters
authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Request Body schema: application/json
name
required
string (Name)

Display name of the Folder.

Responses

Request samples

Content type
application/json
{
  • "name": "My updated folder name"
}

Response samples

Content type
application/json
{
  • "errors": [
    ]
}

Resources: Files

You can ingest a wide range of raw files.

Here's the details of what raw files you can view in the UI:

  • Media (Audio, Video, Images)
  • PDFs
  • Microsoft Documents (DOC, DOCX, PPT, PPTX), rendered as PDFs
  • Microsoft Spreadsheets (Worksheets rendered as tabs)
  • Plain text (CSV, TXT), rendered as PDFs
  • Emails (EML, MSG)
  • Web pages (HTM, HTML)
  • Code

For more information,please check our docs about raw-files ingestion.

Create File

Create a file resource.

Authorizations:
OAuth2
header Parameters
authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Request Body schema: application/json
comment
string (Comment)

Comment type of file.

creation_date
string <date-time> (Creation Date)

Date when file was created.

creator
string (Creator)

User that created the file.

deleter
string (Deleter)

User that deleted the file.

deletion_date
string <date-time> (Deletion Date)

Date when file was deleted.

description
string (Description)

File description.

name
string (Name)

File name.

onna_parent_id
required
string (Parent ID)

The ID of the parent Workspace or Folder.

path
string (Path)

Path to file, at the origin.

ref
required
string (Reference)

The Reference Number or ID for the file at the origin.

share_url
string (Share URL)

Link or invite to share file (at origin).

status
string (Status)

File status: Deleted, Archived, etc.

tags
Array of strings (Tags) <= 1000 items

List of tags associated to the file in the origin.

type
string (Type)

Type of file.

update_date
string <date-time> (Update Date)

Date when the file was last updated.

updater
string (Updater)

The last user to update the file.

url
required
string (URL)

A Unique Resource Locator for the file at the origin.

version
string (Version)

Version.

Responses

Request samples

Content type
application/json
{
  • "onna_parent_id": "da72de92fef04c6a9cc5cfe018fa9cd6"
}

Response samples

Content type
application/json
{
  • "onna_id": "string"
}

Delete File

Delete the file.

Authorizations:
OAuth2
path Parameters
onna_id
required
string (ID)

Unique ID of the file.

header Parameters
authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Responses

Request samples 

curl --request DELETE 'https://api.onna.com/v1/resources/files/fs3f0c5339de42f9964e6afe9bf20169' \
--header 'Authorization: Bearer <ACCESS_TOKEN>' \
--header 'Accept: application/json'

Response samples

Content type
application/json
{
  • "errors": [
    ]
}

Read File

Retrieve a file resource.

Authorizations:
OAuth2
path Parameters
onna_id
required
string (ID)

Unique ID of the file.

header Parameters
authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Responses

Request samples 

curl --request GET 'https://api.onna.com/v1/resources/files/fs3f0c5339de42f9964e6afe9bf20169' \
--header 'Authorization: Bearer <ACCESS_TOKEN>' \
--header 'Accept: application/json'

Response samples

Content type
application/json
{
  • "onna_parent_id": "da72de92fef04c6a9cc5cfe018fa9cd6"
}

Resources: Tickets

The Ticket resource type defines resources with which two parties communicate to track work to resolve issues or deliver incremental value. Customer support requests, service desk tickets, or software development projects are some examples of what can be mapped to this resource type.

Read our developer documentation to learn more about the Ticket resource type.

Create Ticket

Create a ticket resource.

Authorizations:
OAuth2
header Parameters
authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Request Body schema: application/json
assignee_group
string (Assignee Group)

Assignee group.

assignees
Array of strings (Assignees) <= 1000 items

List of users assigned to the ticket.

author
string (Author)

The user that created the ticket.

category
string (Category)

Category.

Array of objects (Comments) <= 5000 items

List of messages associated to the ticket.

creation_date
string <date-time> (Creation Date)

Date when the ticket was created.

description
string (Description)

Description.

followers
Array of strings (Followers) <= 1000 items

List of users following the ticket.

name
required
string (Name)

Title.

onna_parent_id
required
string (Parent ID)

The ID of the parent Folder.

priority
string (Priority)

Priority: high, medium, low, etc.

reactions
Array of strings (Reactions) <= 1000 items

List of reactions.

ref
required
string (Reference)

The Reference Number or ID for the ticket at the origin.

requester
string (Requester)

The user that requested the ticket.

severity
string (Severity)

Severity: high, medium, low, etc.

status
string (Status)

Ticket status: open, closed, archived, etc.

subcategory
string (Subcategory)

Subcategory.

tags
Array of strings (Tags) <= 1000 items

List of tags associated to the ticket in the origin.

type
string (Type)

Type of ticket.

update_date
string <date-time> (Update Date)

Date when the ticket was last updated.

updater
string (Updater)

The last user to update the ticket.

url
required
string (URL)

A Unique Resource Locator for the ticket at the origin.

Responses

Request samples

Content type
application/json
{}

Response samples

Content type
application/json
{
  • "onna_id": "string"
}

Delete Ticket

Delete the ticket.

Authorizations:
OAuth2
path Parameters
onna_id
required
string (ID)

Unique ID of the ticket.

header Parameters
authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Responses

Request samples 

curl --request DELETE 'https://api.onna.com/v1/resources/tickets/tk3f0c5339de42f9964e6afe9bf20358' \
--header 'Authorization: Bearer <ACCESS_TOKEN>' \
--header 'Accept: application/json'

Response samples

Content type
application/json
{
  • "errors": [
    ]
}

Read Ticket

Retrieve a ticket resource.

Authorizations:
OAuth2
path Parameters
onna_id
required
string (ID)

Unique ID of the ticket.

header Parameters
authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Responses

Request samples 

curl --request GET 'https://api.onna.com/v1/resources/tickets/tk3f0c5339de42f9964e6afe9bf20358' \
--header 'Authorization: Bearer <ACCESS_TOKEN>' \
--header 'Accept: application/json'

Response samples

Content type
application/json
{}

Resources: Custom Models

You can define custom resource types by defining and uploading a new schema.

Schemas

A schema defines a custom model. They can be used to upload custom resources.

Upload

A generic endpoint to upload a raw file to an existing resource (ticket, file, etc).

Our upload engine is based on the TUS protocol and treats every upload as a resumable file upload.

Check our get started guide.

Whatever the programming language you're using, it's possible that there's a library that integrates this protocol.

For more information about TUS, see the TUS documentation.

Head Resource File Resumable Upload

HEAD a resource's file, for use with the TUS protocol.

Authorizations:
OAuth2
path Parameters
id
required
string (Id)
header Parameters
tus-resumable
string (Tus-Resumable)

The Tus-Resumable header is included in every request and response.

Tus-Resumable: 1.0.0

For more information on the headers used by TUS, see "the protocol specification".

authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Responses

Request samples 

curl -i 'https://api.onna.com/v1/upload/d3m0d3m0d3m0d3m0d3m0d3m0d3m0d3m0/tus' \
  -X 'HEAD' \
  -H 'Authorization: Bearer <ACCESS_TOKEN>' \
  -H 'content-type: application/offset+octet-stream' \
  -H 'tus-resumable: 1.0.0' \

Response samples

Content type
application/json
{
  • "errors": [
    ]
}

Options Resource File

TUS OPTIONS may be used to gather information about the Server's current configuration.

Authorizations:
OAuth2
path Parameters
id
required
string (Id)
header Parameters
authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Responses

Request samples 

curl -i 'https://api.onna.com/v1/upload/d3m0d3m0d3m0d3m0d3m0d3m0d3m0d3m0/tus' \
  -X 'OPTIONS' \
  -H 'Authorization: Bearer <ACCESS_TOKEN>' \
  -H 'content-type: application/offset+octet-stream' \

Response samples

Content type
application/json
{
  • "errors": [
    ]
}

Resume Resource File Upload

TUS PATCH applies partial modifications to a resource.

Authorizations:
OAuth2
path Parameters
id
required
string (Id)
header Parameters
content-length
string (Content-Length)

The Content-Length header indicates the size of the message body, in bytes, sent to the recipient.

Content-Length: 512

For more information on headers, see "the MDN Web Docs".

content-type
string (Content-Type)

The Content-Type representation header is used to indicate the original media type of the resource (prior to any content encoding applied for sending).

Content-Type: application/json; charset=utf-8

For more information on headers, see "the MDN Web Docs".

upload-offset
string (Upload-Offset)

The Upload-Offset request and response header indicates a byte offset within a resource. The value MUST be a non-negative integer.

Upload-Offset: 64

For more information on the headers used by TUS, see "the protocol specification".

tus-resumable
string (Tus-Resumable)

The Tus-Resumable header is included in every request and response.

Tus-Resumable: 1.0.0

For more information on the headers used by TUS, see "the protocol specification".

authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Responses

Request samples 

curl 'https://api.onna.com/v1/upload/d3m0d3m0d3m0d3m0d3m0d3m0d3m0d3m0/tus' \
  -X 'PATCH' \
  -H 'Authorization: Bearer <ACCESS_TOKEN>' \
  -H 'content-type: application/offset+octet-stream' \
  -H 'tus-resumable: 1.0.0' \
  -H 'upload-offset: 0' \
  --data $'%PDF-1.4\v3ryl0ngstr1ng0fR4wD4t4' \
  --compressed

Response samples

Content type
application/json
{
  • "errors": [
    ]
}

Create Resource File Resumable Upload

TUS CREATION endpoint.

The created file has the same URL as the current endpoint, since a resource can only have a single file.

Authorizations:
OAuth2
path Parameters
id
required
string (Id)
header Parameters
upload-defer-length
string (Upload-Defer-Length)

The Upload-Defer-Length request and response header indicates that the size of the upload is not known currently and will be transferred later. Its value MUST be 1. If the length of an upload is not deferred, this header MUST be omitted.

Upload-Defer-Length: 1

For more information on the headers used by TUS, see "the protocol specification".

upload-length
string (Upload-Length)

The Upload-Length request and response header indicates the size of the entire upload in bytes. The value MUST be a non-negative integer.

Upload-Length: 512

For more information on the headers used by TUS, see "the protocol specification".

upload-metadata
string (Upload-Metadata)

The Upload-Metadata request and response header MUST consist of one or more comma-separated key-value pairs. The key and value MUST be separated by a space. The key MUST NOT contain spaces and commas and MUST NOT be empty. The key SHOULD be ASCII encoded and the value MUST be Base64 encoded. All keys MUST be unique. The value MAY be empty. In these cases, the space, which would normally separate the key and the value, MAY be left out.

Upload-Metadata: filename d29ybGRfZG9taW5hdGlvbl9wbGFuLnBkZg==,is_confidential

For more information on the headers used by TUS, see "the protocol specification".

tus-resumable
string (Tus-Resumable)

The Tus-Resumable header is included in every request and response.

Tus-Resumable: 1.0.0

For more information on the headers used by TUS, see "the protocol specification".

authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Responses

Request samples 

curl 'https://api.onna.com/v1/upload/d3m0d3m0d3m0d3m0d3m0d3m0d3m0d3m0/tus' \
  -X 'POST' \
  -H 'Authorization: Bearer <ACCESS_TOKEN>' \
  -H 'content-length: 0' \
  -H 'tus-resumable: 1.0.0' \
  -H 'upload-length: 44251' \
  -H 'upload-metadata: name Q3JlYXRpdmVjb21tb25zLXdoYXQtaXMtY3JlYXRpdmUtY29tbW9uc19lbmcucGRm' \
  --compressed

Response samples

Content type
application/json
{
  • "errors": [
    ]
}

Create Resource File Single Request

Create single request for resource file upload.

Authorizations:
OAuth2
path Parameters
id
required
string (Id)
header Parameters
authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Responses

Request samples 

curl -i 'https://api.onna.com/v1/upload/d3m0d3m0d3m0d3m0d3m0d3m0d3m0d3m0/tus' \
  -X 'PUT' \
  -H 'Authorization: Bearer <ACCESS_TOKEN>' \
  -H 'content-type: application/offset+octet-stream' \

Response samples

Content type
application/json
{
  • "errors": [
    ]
}

Utils

API Utils, such as the health endpoint.

Health Check

Check service status, version and build.

Authorizations:
OAuth2

Responses

Request samples 

curl --request GET \
--url 'https://api.onna.com/v1/health' \
--header 'Authorization: Bearer <ACCESS_TOKEN>' \
--header 'Accept: application/json' \

Response samples

Content type
application/json
{
  • "release_id": "1.0.0",
  • "status": "pass",
  • "version": "v1"
}

CustomFields

List Custom Fields

List custom fields.

Authorizations:
OAuth2
query Parameters
cursor
string (Cursor)
Example: cursor=2022-02-22T11:11:11.12345
header Parameters
authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Responses

Request samples 

curl ...

Response samples

Content type
application/json
{
  • "items": [
    ]
}

Create Custom Field

Create a custom field.

Authorizations:
OAuth2
header Parameters
authorization
string (Authorization)

Authorization: Bearer ACCESS_TOKEN

The Authorization header must contain a Bearer Token, for more information see "Obtaining an access token".

Request Body schema: application/json
description
required
string (Description)

Description

name
required
string (Name)

Name

required
required
boolean (Required)

Required

type
required
string (Type)

Type

Responses

Request samples

Content type
application/json
{
  • "name": "My custom field",
  • "required": false,
  • "type": "keyword"
}

Response samples

Content type
application/json
{
  • "onna_id": "cf-my-custom-field-b20696ae9"
}