ASCI API

| Home | Swagger | All Forms | Documentation | HTS →

Vendors module page - how it works, an interactive test form, and the endpoint reference, all in one place. Set your tenant API Key in the Setup block below; every request sends the ApiKey header. See All Forms for the combined surface or Home for the module index.

How it works

Accounts-payable vendor master record create / find.

Vendors

The Vendors module is the accounts-payable (A/P) vendor master - a first-class reference entity like customers / manufacturers / products. POST /api/Vendors performs a synchronous upsert into the API store keyed by tenant + code (there is no legacy vendor writer yet, so create is a store-only upsert - it does not enqueue a legacy write). Use Find existing to GET /api/Vendors?code=&name= and click a row to load it into the form before editing. The vendor master backs the Pending Charges (billing) module, which resolves its provider payee against these records. Source: legacy A/P vendor master APVE{CID} (key AP_VEND_CODE). Vendors can also be loaded in bulk via POST /api/Import/Entities (the vendors toggle).

Setup

API key + base URL used by every request below.

Credentials

Leave Base URL blank to call this same server with relative paths (the normal case). Set it (e.g. https://asci-api.asciofmiami.com) to point the forms at another host. Every request below sends the ApiKey header.

Sent on every create / submit POST. Click Generate for a fresh one, or a new one is auto-generated per submit if blank.

Test form

Interactive form - POSTs to the API and shows the JSON response + HTTP status.

Create an A/P vendor master record: POST /api/Vendors (idempotent store upsert, keyed by tenant + code). Scope: ipjson.submit. The code is client-supplied (it is the legacy AP_VEND_CODE).

Find existing

GETs /api/Vendors?code=&name=. Click a row to load it into the form.

Create

Endpoints

Vendors endpoint family (api/Vendors). Full request schema below.

Vendors endpoints

MethodPathScopePurpose
POST/api/Vendorsipjson.submitCreate / upsert a vendor (body keyed by code). Returns { code, inserted, updated }.
GET/api/Vendorsqueue.readSearch (?q= or ?code=&name=&limit=). Returns {count, rows}.
GET/api/Vendors/{code}queue.readFetch one vendor by exact code. 404 if absent.
DELETE/api/Vendors/{code}ipjson.submitDelete one vendor by code. Returns { deleted: 1 }.
DELETE/api/Vendors?confirm=trueipjson.submitDelete ALL vendors for this tenant (guarded by ?confirm=true). Returns { deleted: <count> }.
Bulk import. Vendors are also part of the bulk master-data pipeline. Include a vendors toggle + vendors[] array in POST /api/Import/Entities, and the push-to-legacy export GET /api/Import/EntitiesExport?types=vendors emits the #section:vendors TSV block.

Schema

Request body for POST /api/Vendors. The same object is returned by the GET endpoints; GET /api/Vendors wraps the rows as { "count": n, "rows": [ … ] } (each row also carries created_at / updated_at).

Vendor record

FieldTypeReq?MaxDescription
codestringYes15Vendor code / AP_VEND_CODE. Primary key (per tenant).
namestringNo-Vendor name.
vendor_typestringNo-Vendor type (AP_VENDOR_TYPE).
contactstringNo-Contact name (AP_CONTACT).
address_1 / address_2 / address_3stringNo-Address lines.
city / state / zip / countrystringNo-City, state, postal code, country.
overseasstringNo-Overseas flag.
phone_area / phonestringNo-Phone area code + number.
fax_area / faxstringNo-Fax area code + number.
terms_codestringNo-Payment-terms code.
form_codestringNo-Form code.
gl_acct_apstringNo-A/P GL control account (GL_ACCT_AP).
gl_acct_nostringNo-Default expense GL account (GL_ACCT_NO).
our_acct_nostringNo-Our account number with this vendor (OUR_ACCT_NO).
recipient_idstringNo-1099 recipient id (RECIPIENT_ID).
payto_namestringNo-Remit-to (pay-to) name.
payto_addr_1 / payto_addr_2stringNo-Pay-to address lines.
payto_city / payto_state / payto_zip / payto_countrystringNo-Pay-to city, state, ZIP, country.
payto_attnstringNo-Pay-to attention line.
payto_phonestringNo-Pay-to phone.