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

Vic.ai Payment Terms API

Payment terms are part of your *ERP* **Masterdata**, and representpayment terms that Vic.ai can automatically assign to invoices. Somevendors may have a default payment term, and some invoices may have aspecific payment term. In either case, Vic.ai can automatically assignpayment terms to invoices.

Vic.ai Payment Terms API is one of 33 APIs that Vic.ai publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payment Terms. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 6 operations across 3 paths, and defines 7 schemas. It is described by OpenAPI 3.1.0, at version v10.40.4.

Requests are made against 3 base URLs: https://api.no.stage.vic.ai, https://api.us.vic.ai, https://api.no.vic.ai.

6 operations 3 paths 7 schemas 1 DELETE2 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v10.40.4
Base URL
https://api.us.vic.ai
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Vic.ai Payment Terms API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerAuth). By default, every request must be authenticated.

Paths & Operations 6

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

Payment Terms 6

Payment terms are part of your ERP Masterdata, and represent payment terms that Vic.ai can automatically assign to invoices. Some vendors may have a default payment term, and some…

GET
/v0/paymentTerms
Get a list of payment terms
listPaymentTerms → 2004294XX
POST
/v0/paymentTerms
Create a new payment term
createPaymentTerm body → 201403422
POST
/v0/paymentTerms/synchronize
Synchronize Payment Terms
synchronizePaymentTerms → 2044294XX
GET
/v0/paymentTerms/{id}
Get a payment term
getPaymentTerm 2 params → 200403404
PUT
/v0/paymentTerms/{id}
Update a payment term
updatePaymentTerm 2 params body → 200403422
DELETE
/v0/paymentTerms/{id}
Delete a payment term
deletePaymentTerm 2 params → 2044294XX

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are PaymentTerm (9 properties), CreatePaymentTerm (8 properties), UpdatePaymentTerm (8 properties), Error (2 properties). Each schema is shown below with its type and property counts.

UpdatePaymentTerm
object
8 properties 2 required
PaymentTerm
object
9 properties 2 required
CreatePaymentTerm
object
8 properties 2 required
ExternalId
string
The external id set by the ERP system. It does not have to be a UUID and can be any non empty string desired.
ErrorString
string
Error
object
generic error message in JSON format. Note the 'code' field should match the HTTP status code of the wrapping HTTP request.
2 properties 2 required
PaymentTermCondition
string
issuedate - The due or discount date is calculated by adding the daysToPay or discountDays to the invoice issue date. dateonnext0month - The due or discount da…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vicai-payment-terms-api-openapi.yml Raw ↑

Other APIs Vic.ai publishes across the network.

Vic.ai Accounts API
Vic.ai Allowed Senders API
Vic.ai Attachments API
Vic.ai Authentication API
Vic.ai Beta Features API
Vic.ai Bills API
Vic.ai Companies API
Vic.ai Company Settings API
Vic.ai Credit Confirmations API
Vic.ai CSV Reports API
Vic.ai Dimensions API
Vic.ai Email Endpoints API
Where this information came from

This is an independent, third-party profile of Vic.ai Payment Terms 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.