How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Qubiqle Receipts API

The receipts API from Qubiqle — 3 operation(s) for receipts.

This API exposes 5 operations across 3 paths, and defines 21 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api.ottimate.com/v1, https://sandbox-api.ottimate.com/v1.

5 operations 3 paths 21 schemas 2 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.ottimate.com/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Qubiqle Receipts API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (OAuth2).

  • OAuth2 — OAuth2 authentication flows. Auth server URLs will vary by environment

Paths & Operations 5

Across 3 paths, the API surfaces 5 operations — 2 GET, 1 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Receipts 5
GET
/receipts
Retrieve a paginated list of receipts
get-receipts-root 13 params → 200400401
POST
/receipts
Create a single receipt
post-receipts-root 4 params body → 201400
GET
/receipts/{id}
Retrieve a specific receipt by ID
get-receipts-id 4 params → 200404
PATCH
/receipts/{id}
Update an existing receipt
patch-receipts-id 4 params body → 200400404
POST
/receipts/bulk
Bulk create or update receipts
post-receipts-bulk 4 params body → 202400

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are ReceiptDetailReceipt (14 properties), ReceiptCreateRequest (12 properties), ReceiptBulkUpsertRequestReceiptsItems (12 properties), ReceiptDetailReceiptItemsItems (12 properties). Each schema is shown below with its type and property counts.

ReceiptCreateRequest
object
To identify the PO, provide either ottimatepoid OR the lookup combination: erpvendorid + ottimatelocationid + (ponumber OR poexternalid).
12 properties 4 required
ReceiptBulkUpsertAsyncResponseStatus
string
ReceiptSummary
object
9 properties 2 required
ReceiptsIdPatchRequestBodyContentApplicationJsonSchemaItemsItems
object
8 properties
ReceiptBulkUpsertRequestReceiptsItemsItemsItems
object
Each item requires quantity and one of: ottimatepoitemid, poexternalitemid, or sku.
7 properties 1 required
ReceiptBulkUpsertAsyncResponse
object
6 properties 2 required
Receipts_get_receipts_root_Response_200
object
5 properties
ReceiptBulkUpsertRequest
object
2 properties 2 required
ReceiptSummaryStatus
string
ReceiptDetailReceiptStatus
string
ReceiptUpdateResponse
object
10 properties 2 required
ReceiptCreateResponseStatus
string
ReceiptCreateResponse
object
9 properties 2 required
ReceiptCreateRequestItemsItems
object
Each item requires quantity and one of: ottimatepoitemid, poexternalitemid, or sku.
7 properties 1 required
ReceiptUpdateResponseStatus
string
ReceiptBulkUpsertRequestReceiptsItems
object
To identify the PO, provide either ottimatepoid OR erpvendorid + ottimatelocationid + (ponumber OR poexternalid).
12 properties 4 required
ReceiptBulkUpsertAsyncResponseSummary
object
2 properties
ReceiptDetail
object
2 properties 1 required
ErrorResponse
object
4 properties 2 required
ReceiptDetailReceipt
object
14 properties 2 required
ReceiptDetailReceiptItemsItems
object
12 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

qubiqle-receipts-api-openapi.yml Raw ↑
Where this information came from

This is an independent, third-party profile of Qubiqle Receipts API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.